[
https://issues.apache.org/jira/browse/STORM-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated STORM-3133:
----------------------------------
Labels: pull-request-available (was: )
> Extend metrics on Nimbus and LogViewer
> --------------------------------------
>
> Key: STORM-3133
> URL: https://issues.apache.org/jira/browse/STORM-3133
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-server
> Affects Versions: 2.0.0
> Reporter: Zhengdai Hu
> Assignee: Zhengdai Hu
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.0
>
>
> Include but not limited to
> Logviewer
> 1. Clean-up time
> 2. Time to complete one clean up loop Time.
> 3. Disk usage by logs before cleanup and After cleanup loop. ( Just like GC.?)
> 4. Failures/exceptions.
> 5. Search request Cnt: By category - Archived/non-archived
> 6. Search Request - Response time
> 7. Search Request - 0 result Cnt
> 8. Search Result - open files
> 9. File partial read count
> 10. File Download request Cnt/ And Size served
> 11. Disk IO by logviewer
> 12. CPU usage ( for unzipping files)
> Nimbus Additional:
> - Topology stormjar.ser/stormconf.ser/stormser.ser file upload time.
> - Scheduler related metrics would be a long list generic and specific to
> different strategies.
> - Most if not all cluster summary can be pushed as Metrics.
> - Restart cnt
> - Nimbus loss of leadership(?)
> - UI not responding (https://jira.ouroath.com/browse/YSTORM-4838)
> - Negative resource scheduling events
> (https://jira.ouroath.com/browse/YSTORM-4940)
> - Excessive scheduling time (?)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
