[
https://issues.apache.org/jira/browse/STORM-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951231#comment-16951231
]
Daisy Chen edited comment on STORM-3019 at 10/14/19 6:29 PM:
-------------------------------------------------------------
StormReporter extends com.codahale.metrics.Reporter, which is a metric reporter
and not designed for generating the info you mentioned, is there a reason that
you think it should be implemented on StormReporter? [~thecoop1984]
was (Author: daisychen):
StormReporter extends com.codahale.metrics.Reporter, which is a metric reporter
and not designed for generating the info you mentioned, is there a reason that
you think it should be implemented on StormReporter?
> StormReporter doesn't have information on where it's running
> ------------------------------------------------------------
>
> Key: STORM-3019
> URL: https://issues.apache.org/jira/browse/STORM-3019
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Simon Cooper
> Priority: Major
> Labels: metrics
>
> Metrics2 StormReporter implementations don't have a lot of information on
> where they're running. In particular, they are missing:
> * Whether they are running for nimbus, supervisor, or worker, and what the
> worker is.
> * The full deployed config - it's just provided with the basic topology
> configuration, not the full effective configuration as specified at topology
> deployment
> * A TopologyContext object
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
