You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently histograms are reported using a bunch of manually created counters with names like __1ms, __2ms, __10ms and a label histogram="ExecutionTime" by which you can identify the bucket. This format is supported only in Solomon. Example (prometheus format):
monlib already has all that we need - special class THistogram that can report histogram in format supported both in Solomon and Grafana. One need to support reporting histogram using this class. To provide backward compatibility it is proposed to leave the old format (with multiple counters). It would be useful to add two new parameters in diagnostics config that will manage histogram report mode:
ReportHistogramAsSingleCounter, with default false value
ReportHistogramAsMultipleCounters, with default true value
The text was updated successfully, but these errors were encountered:
Problem
Currently histograms are reported using a bunch of manually created counters with names like __1ms, __2ms, __10ms and a label histogram="ExecutionTime" by which you can identify the bucket. This format is supported only in Solomon. Example (prometheus format):
The grafana is waiting for histogram in the following format (with "le" label that means "less or equal" bucket):
Solution
monlib already has all that we need - special class
THistogram
that can report histogram in format supported both in Solomon and Grafana. One need to support reporting histogram using this class. To provide backward compatibility it is proposed to leave the old format (with multiple counters). It would be useful to add two new parameters in diagnostics config that will manage histogram report mode:ReportHistogramAsSingleCounter
, with defaultfalse
valueReportHistogramAsMultipleCounters
, with defaulttrue
valueThe text was updated successfully, but these errors were encountered: