[ 
https://issues.apache.org/jira/browse/IGNITE-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey N. Gura updated IGNITE-17353:
------------------------------------
    Description: 
Design and implement metrics framework for Apache Ignite 3 internal purposes.

*Requirements:*
 # Ease of maintaining existing metrics and adding new ones (related metrics 
should be placed together, compile time checking where possible (methods 
instead of text identifiers))

 # Avoidance of data races (related metrics life cycle should be tied with 
corresponding component)

 # Possibility to enable\disable some subset of metrics at runtime

 # Metrics consistency (for similar components must be the same sets of related 
metrics independently of component configuration)

 # Reasonable performance characteristics (avoid of boxed types, concurrency 
characteristics accordingly to use cases, etc)

On this stage metrics will be exposed through JMX interface only (JMX exporter) 
and metrics management will be possible through CLI (enable/disable/list)

  was:Design and implement metrics framework for Apache Ignite 3 internal 
purposes.


> Ignite 3 Metrics
> ----------------
>
>                 Key: IGNITE-17353
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17353
>             Project: Ignite
>          Issue Type: Epic
>            Reporter: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>
> Design and implement metrics framework for Apache Ignite 3 internal purposes.
> *Requirements:*
>  # Ease of maintaining existing metrics and adding new ones (related metrics 
> should be placed together, compile time checking where possible (methods 
> instead of text identifiers))
>  # Avoidance of data races (related metrics life cycle should be tied with 
> corresponding component)
>  # Possibility to enable\disable some subset of metrics at runtime
>  # Metrics consistency (for similar components must be the same sets of 
> related metrics independently of component configuration)
>  # Reasonable performance characteristics (avoid of boxed types, concurrency 
> characteristics accordingly to use cases, etc)
> On this stage metrics will be exposed through JMX interface only (JMX 
> exporter) and metrics management will be possible through CLI 
> (enable/disable/list)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to