[
https://issues.apache.org/jira/browse/STORM-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cody updated STORM-1329:
------------------------
Attachment: A comparison between JStorm metrics and Storm metrics and
JStorm metrics design.pdf
added a comparison between Storm metrics & JStorm metrics and related JStorm
metrics design document.
> Evaluate/Port JStorm metrics system
> -----------------------------------
>
> Key: STORM-1329
> URL: https://issues.apache.org/jira/browse/STORM-1329
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-core
> Reporter: Robert Joseph Evans
> Assignee: Cody
> Labels: jstorm-merger
> Attachments: A comparison between JStorm metrics and Storm metrics
> and JStorm metrics design.pdf
>
>
> Storm:
> IMetric and IMetricConsumer
> JStorm:
> All levels of metrics, including stream metrics, task metrics, component
> metrics, topology metrics, even cluster metrics, are sampled & calculated.
> Some metrics, e.g. ""tuple life cycle"", are very useful for debugging and
> finding the hotspots of a topology.
> Support full metrics data. Previous metric system can only display mean
> value of meters/histograms, the new metric system can display m1, m5, m15 of
> meters, and common percentiles of histograms.
> Use new metrics windows, the mininum metric window is 1 minute, thus we
> can see the metrics data every single minute.
> Supplies a metric uploader interface, third-party companies can easily
> build their own metric systems based on the historic metric data.
> Ideally we should have a way to display most/system metrics in the UI.
> IMetric is too generic to make this happen, but we cannot completely drop
> support for it. But perhaps we need to depricate it if the JStorm metrics
> are much better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
