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
In the old framework, all the metrics have the identical metric labels. The only difference is that for those metrics which have no attributes of app and partition, their values will be left empty as following example:
empiredan
changed the title
Feature(new_metrics): go-collector collect the metrics from meta server and replica
Feature(new_metrics): go-collector collects the metrics from meta server and replica server
Dec 29, 2023
empiredan
changed the title
Feature(new_metrics): go-collector collects the metrics from meta server and replica server
Feature(new_metrics): go-collector supports to collect and expose the metrics to Prometheus
Dec 29, 2023
…uery (#1827)
#1820
Labels are needed by metric models like Prometheus Data Model.
Therefore, cluster name, role name, host name and port should be
provided in the response to metrics query as the labels. All of these
fields would be added in the form of name/value pairs of json object.
Original entity array would be the value of a json object with name
"entities".
1. Prometheus metrics of old framework
In the old framework, all the metrics have the identical metric labels. The only difference is that for those metrics which have no attributes of
app
andpartition
, their values will be left empty as following example:For those metrics which have attributes of
app
andpartition
their values will certainly left non-empty:2. The Design of Prometheus metrics of new framework
Referring to the old framework and the features of new metrics system, the new Prometheus labels could be designed as below:
The text was updated successfully, but these errors were encountered: