[
https://issues.apache.org/jira/browse/IGNITE-25505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-25505:
----------------------------------
Description:
*Motivation*
As for now, composite metrics are exported as plain strings, which is not the
best way for complex structured objects and it doesn't give a convenient way to
watch them in external tools that use JMX. OpenMBean has a conventional way to
solve this.
*Definition of done*
We should add OpenMBean CompositeData (and probably TabularData) support for
jmx exporter:
* as a prerequisite, CompositeMetric in metric framework should be extended in
order to provide all composite metric meta information for jmx exporter to
create CompositeData instance (items, their types, etc.);
* all CompositeMetrics in AI should support these CompositeMetric extension;
* after that, jmx exporter should be improved to create CompositeData for
CompositeMetric.
was:
*Motivation*
As for now, composite metrics are exported as plain strings, which is not the
best way for complex structured objects and it doesn't give a convenient way to
watch them in external tools that use JMX. OpenMBean has a conventional way to
solve this.
*Definition of done*
We should add OpenMBean CompositeData (and probably TabularData) support for
jmx exporter:
* as a prerequisite, CompositeMetric in metric framework should be extended in
order to provide all composite metric information for jmx exporter to create
CompositeData instance (items, their types, etc.);
* all CompositeMetrics in AI should support these CompositeMetric extension;
* after that, jmx exporter should be improved to create CompositeData for
CompositeMetric.
> Add OpenMBean CompositeData and TabularData support for JMX metric exporter
> ---------------------------------------------------------------------------
>
> Key: IGNITE-25505
> URL: https://issues.apache.org/jira/browse/IGNITE-25505
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Chudov
> Priority: Major
> Labels: ignite-3
>
> *Motivation*
> As for now, composite metrics are exported as plain strings, which is not the
> best way for complex structured objects and it doesn't give a convenient way
> to watch them in external tools that use JMX. OpenMBean has a conventional
> way to solve this.
> *Definition of done*
> We should add OpenMBean CompositeData (and probably TabularData) support for
> jmx exporter:
> * as a prerequisite, CompositeMetric in metric framework should be extended
> in order to provide all composite metric meta information for jmx exporter to
> create CompositeData instance (items, their types, etc.);
> * all CompositeMetrics in AI should support these CompositeMetric extension;
> * after that, jmx exporter should be improved to create CompositeData for
> CompositeMetric.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
