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
Hi team, the exporter currently leverage three different endpoints:
/
/bmc
/metrics
the root (/) endpoint is used as a simple helper webpage.
the /bmc endpoint is used as the scrape endpoint for prometheus server.
the /metrics endpoint is used as a global statistic endpoint.
Within prometheus world, you can reassign the scrape endpoint, BUT exporter authors tends to all use the same logical naming convention as it allow easier and straight forward automation process and exporter integration.
I'm currently working on integrating this exporter among openstack kolla/kolla-ansible project.
The various exporter we integrate usually tend to rather use the following pattern:
/graph
/metrics
the /graph endpoint is used as a simple helper webpage (as for prometheus server WebUI used to request its dataset).
the /metrics endpoint is used as the scrape endpoint for prometheus server to retrieve metrics data AND exporter statistics (promhttp_metric_handler_errors_total for example).
If you really want to split the exporter statistics from the /metrics endpoint, a better suited endpoint name could be /stats
What do you think guys?
The text was updated successfully, but these errors were encountered:
Hi team, the exporter currently leverage three different endpoints:
the root (/) endpoint is used as a simple helper webpage.
the /bmc endpoint is used as the scrape endpoint for prometheus server.
the /metrics endpoint is used as a global statistic endpoint.
Within prometheus world, you can reassign the scrape endpoint, BUT exporter authors tends to all use the same logical naming convention as it allow easier and straight forward automation process and exporter integration.
I'm currently working on integrating this exporter among openstack kolla/kolla-ansible project.
The various exporter we integrate usually tend to rather use the following pattern:
the /graph endpoint is used as a simple helper webpage (as for prometheus server WebUI used to request its dataset).
the /metrics endpoint is used as the scrape endpoint for prometheus server to retrieve metrics data AND exporter statistics (promhttp_metric_handler_errors_total for example).
If you really want to split the exporter statistics from the /metrics endpoint, a better suited endpoint name could be /stats
What do you think guys?
The text was updated successfully, but these errors were encountered: