Ensuring the exporter works out of the box without configuration, and providing a selection of example configurations for transformation if required, is advised. YAML is the standard Prometheus configuration format, all configuration should use YAML by default.

We are happy to give advice on how to make your exporter as useful and consistent as possible. Some third-party software exposes metrics in the Prometheus format, so no separate exporters are needed:

February 26, 2025 - Metric collection: An exporter ... switch. Metric transformation: The collected data is then converted into the Prometheus exposition format, making it compatible with Prometheus' scraping mechanism....

January 25, 2026 - Prometheus exporters thus bridge the gap between Prometheus and applications that don’t export metrics in the Prometheus format.

Regardless of whether a Prometheus client library is used, the Prometheus Exporter MUST support version 0.0.4 of the Text-based format.

All exporters the following exposition formats: OpenMetrics text format Prometheus text format Prometheus protobuf format Moreover, gzip encoding is supported for each of these formats. OpenMetrics 2.0 Preview The library also includes an experimental OpenMetrics 2.0 writer.

December 19, 2024 - Expose an HTTP endpoint in the exporter application for Prometheus to scrape. Ensure the metrics are formatted correctly, either as key-value pairs or in Prometheus exposition format.

August 22, 2024 - Exporter is an abstraction layer between the application and Prometheus, which takes application-formatted metrics and converts them to Prometheus metrics for consumption.

May 5, 2021 - Prometheus exporters can be stateful or stateless. A stateful exporter is responsible for gathering data and exports them using the general metrics format such as counter, gauge, etc. Stateless exporters are exporters that translate metrics from one format to Prometheus metrics format using counter metric family, gauge metric family, etc.

January 3, 2021 - Prometheus is a clear leader in the cloud native world for metrics. Prometheus follows an HTTP pull model: It scrapes Prometheus metrics from endpoints routinely. Typically the abstraction layer between the application and Prometheus is an exporter, which takes application-formatted metrics and converts them to Prometheus metrics for consumption.

May 9, 2021 - Prometheus exporters can be stateful or stateless. A stateful exporter is responsible for gathering data and exports them using the general metrics format such as counter, gauge, etc. Stateless exporters are exporters that translate metrics from one format to Prometheus metrics format using counter metric family, gauge metric family, etc.

September 30, 2022 - We cannot provide a description for this page right now

Prometheus exporter for hardware and OS metrics exposed by *NIX kernels, written in Go with pluggable metric collectors.

July 1, 2019 - For systems that can’t be instrumented with a Prometheus-compliant metrics library, Exporters provide a scrape endpoint using a trivial text-oriented “exposition” format that’s straightforward to implement.

September 20, 2020 - Your exporter is now ready to use! Every time you hit the metrics route, it will perform the api call, and return the result in Prometheus Text file format.

November 15, 2023 - The Prometheus Text Format is a widely adopted format to expose metrics, and it is, next to the OpenMetrics text format and the Prometheus Protobuf format, adopted by Prometheus. It must be exposed over HTTP to be scraped.

May 21, 2023 - Such an exporter can be included directly in the code of your application, or it can be run as a separate service that will poll one of your services and receive data from it, which will then be converted into the Prometheus format and sent to the Prometheus server.

May 11, 2022 - In this option, Exporter will expose all data over HTTP in prometheus data format.

February 25, 2023 - Such an exporter can be included directly in the code of your application, or it can be run as a separate service that will poll one of your services and receive data from it, which will then be converted into the Prometheus format and sent to the Prometheus server.

If modules.<module_name>.body paramater is set in config, it will be sent by the exporter as the body content in the scrape request. The HTTP method will also be set as 'POST' in this case. body: content: | My static information: {"time_diff": "1m25s", "anotherVar": "some value"} The body content can also be a Go Template. All the functions from the Sprig library can be used in the template. All the query parameters sent by prometheus in the scrape query to the exporter, are available as values while rendering the template.