[ https://issues.apache.org/jira/browse/STORM-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418341#comment-15418341 ]
ASF GitHub Bot commented on STORM-2006: --------------------------------------- Github user harshach commented on the issue: https://github.com/apache/storm/pull/1595 @HeartSaVioR I would like to see this merged into 1.x-branch. Given suggestions here can you make the changes , introducing IAggregatedMetrics interface and leave the existing the interface as it is. > Storm metrics feature improvement: support per-worker level metrics > aggregation > ------------------------------------------------------------------------------- > > Key: STORM-2006 > URL: https://issues.apache.org/jira/browse/STORM-2006 > Project: Apache Storm > Issue Type: Improvement > Components: storm-core > Affects Versions: 1.1.0 > Reporter: Jungtaek Lim > Assignee: Jungtaek Lim > > Storm provides per-task level metrics which could be huge when topology has a > number of tasks. > Task level metric is useful for determining load balance between tasks, but > it doesn't need to be time-series fashion. > Before introducing topology level component like TopologyMaster for JStorm, > we can utilize SystemBolt to aggregate task level metrics to per-worker level > metrics. > We should provide options and this feature should be turned off by default to > keep backward compatibility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)