Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.0
Description
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
Attachments
Issue Links
- is a parent of
-
STORM-3144 Extend metrics on Nimbus
- Closed
- relates to
-
STORM-3187 Nimbus code refactoring and cleanup
- Open
-
STORM-3099 Extend metrics on supervisor, workers, and DRPC
- Closed
-
STORM-3186 Customizable configuration for metric reporting interval
- Closed
-
STORM-3188 Removing try-catch block from getAndResetWorkerHeartbeats
- Closed
- links to