Hi there Serega, What you see in the UI are probably compound executor "ID"s. They are actually ranges of task IDs assigned to respective executors. For example, [26-27] means executor with tasks 26 and 27 assigned to it. Task can determine its ID via TopologyContext.getThisTaskId() inside the component code. On the MetricsConsumer side, each DataPoint contains srcTaskId field. Those can be used further to match task-provided data against executor IDs. To avoid parsing executor ID strings, you may want to use Nimbus Thrift API to obtain ExecutorInfo structures that already have task_start and task_end as separate fields.
Regards, Yury 2016-04-26 22:55 GMT+03:00 Serega Sheypak <[email protected]>: > Hi, there is an id for each task displayed in UI. Id values are: [26-27] > or [44-45]. I want to publish application-specific metrics to Influx, I > want to publish the same id in metric name, so I can match basic Storm > metrics with my app metrics and find bottlenecks/skews/e.t.c > > What API shoud I use to get the same combnation of ids? >
