[
https://issues.apache.org/jira/browse/QPID-8454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158756#comment-17158756
]
Alex Rudyy commented on QPID-8454:
----------------------------------
[~rgodfrey], thanks for the suggestion to implement metric endpoint on the
virtual host level. I agree that the virtual host is the best candidate for it.
I also was thinking to add metric endpoint on a broker level, where each metric
can have a hierarchy label which should allow to associate the metric with a
concrete configured object, but, I am not sure about that. It is yet not
decided what labels can be set on metrics. It seems that enhancing metrics
with labels for object names and types is a good idea. I was considering to
compose the metric name from a category name and a statistics name and add
the label for a hierarchy (path to the object), but, that was just my initial
thoughts. I was going to look through the promethium documentation and various
implementations before deciding how to implement it on Qpid broker side. I am
open to any ideas in this area and happy to discuss all possible suggestions.
> [Broker-J] Expose configured object statistics in prometheus format
> -------------------------------------------------------------------
>
> Key: QPID-8454
> URL: https://issues.apache.org/jira/browse/QPID-8454
> Project: Qpid
> Issue Type: New Feature
> Components: Broker-J
> Reporter: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-8.0.1, qpid-java-broker-7.1.9
>
>
> The configured object statistics currently can be retrieved using a call to
> method {{getStatistics()}}, configured object REST API endpoint
> {{/api/latest/<category>/<path>}} or query API (
> {{/api/latest/querybroker/<category>}} or {{/api/latest/queryvhost/<virtual
> host node name>/<virtual host name>/<category>}} ). The statistics is
> returned back to the caller in json format. That works for majority of uses
> cases. However, when it is required to integrate Qpid Broker-J with
> Prometheus, the Qpid users are required to implement an intermediate layer
> where Qpid metrics needs to be converted into a Prometheus format
> [https://prometheus.io/docs/concepts/data_model/].
> In order to easy the burden of integration Qpid Broker-J with Prometheus, the
> support for reporting statistics metrics in Prometheus format can be added
> into Qpid Broker-J.
> Potentially, we can add an endpoint exposing all Qpid statistics as
> Prometheus metrics [https://prometheus.io/docs/concepts/metric_types/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
