You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2021/08/01 12:12:00 UTC
[jira] [Commented] (TEZ-4318) Tez debugging tools webapp
[ https://issues.apache.org/jira/browse/TEZ-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391138#comment-17391138 ]
László Bodor commented on TEZ-4318:
-----------------------------------
attached history files for trying out:
simple: [^history.txt]
proto: [^dag_1627089048261_0000_1_1] [^dag_1627089048261_0000_1_1_1]
ATS: [^dag_1627810632098_0001_1.zip]
> Tez debugging tools webapp
> --------------------------
>
> Key: TEZ-4318
> URL: https://issues.apache.org/jira/browse/TEZ-4318
> Project: Apache Tez
> Issue Type: New Feature
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Attachments: dag_1627089048261_0000_1_1, dag_1627089048261_0000_1_1_1, dag_1627810632098_0001_1.zip, history.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is about creating a very simple UI for postprocessing info about tez dags.
> The primary focus is on [analyzers|https://github.com/apache/tez/tree/master/tez-tools/analyzers/job-analyzer].
> I use analyzers quite often, thinking about a browser-based solution, which can be started easily locally, and lets the user do something like:
> 1. upload history logging file (simple, proto)
> 2. run a set of analyzers (change config opts from UI)
> 3. return 1 or more xls / cvs files with the result(s) (format can be picked on UI)
> [tez-tools|https://github.com/apache/tez/tree/master/tez-tools] has lot more tools there, but for me, the real benefit would be having analyzers in the first round
> also interested in the dockerized approach
--
This message was sent by Atlassian Jira
(v8.3.4#803005)