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

Andrey Gura updated IGNITE-12044:
---------------------------------
    Description: 
JmxExporterSpi exposes histogram values incorrectly. It looks like:

{noformat}
durationHistogram                long[5]
{noformat}

I think exporter should register attribute for each histogram bucket. Something 
like this:

{noformat}
durationHistogram.10                 0
durationHistogram.50                 0
durationHistogram.100                0
durationHistogram.250                0
durationHistogram.500                0
{noformat}



  was:
JmxExporterSpi exposes histogram values incorrectly. It looks like:

{noformat}
durationHistogram                long[5]
{noformat}

I think exporter should register attribute for each histogram bucket. Something 
like this:

{noformat}
durationHistogram.10                  0
durationHistogram.50                  0
durationHistogram.100                0
durationHistogram.250                0
durationHistogram.500                0
{noformat}




> [IEP-35] JmxExporterSpi displays histogram values incorrectly
> -------------------------------------------------------------
>
>                 Key: IGNITE-12044
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12044
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Andrey Gura
>            Priority: Major
>              Labels: IEP-35
>             Fix For: 2.8
>
>
> JmxExporterSpi exposes histogram values incorrectly. It looks like:
> {noformat}
> durationHistogram                long[5]
> {noformat}
> I think exporter should register attribute for each histogram bucket. 
> Something like this:
> {noformat}
> durationHistogram.10                 0
> durationHistogram.50                 0
> durationHistogram.100                0
> durationHistogram.250                0
> durationHistogram.500                0
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to