plone

prometheus-squid-exporter-1.10.3-0.1.git7693646.lbn36.x86_64
Prometheus Exporter Squid
Located in LBN / … / Network Monitoring / BastionLinux 36
prometheus-statsd-exporter-0.26.0-1.lbn36.x86_64
statsd_exporter receives StatsD-style metrics and exports them as Prometheus metrics. Overview With StatsD To pipe metrics from an existing StatsD environment into Prometheus, configure StatsD's repeater backend to repeat all received metrics to a statsd_exporter process. This exporter translates StatsD metrics to Prometheus metrics via configured mapping rules. +----------+ +-------------------+ +--------------+ | StatsD |---(UDP/TCP repeater)--->| statsd_exporter |<---(scrape /metrics)---| Prometheus | +----------+ +-------------------+ +--------------+ Without StatsD Since the StatsD exporter uses the same line protocol as StatsD itself, you can also configure your applications to send StatsD metrics directly to the exporter. In that case, you don't need to run a StatsD server anymore. We recommend this only as an intermediate solution and recommend switching to native Prometheus instrumentation in the long term. Tagging Extensions The exporter supports Librato, InfluxDB, and DogStatsD-style tags, which will be converted into Prometheus labels. For Librato-style tags, they must be appended to the metric name with a delimiting #, as so: metric.name#tagName=val,tag2Name=val2:0|c See the statsd-librato-backend README for a more complete description. For InfluxDB-style tags, they must be appended to the metric name with a delimiting comma, as so: metric.name,tagName=val,tag2Name=val2:0|c See this InfluxDB blog post for a larger overview. For DogStatsD-style tags, they're appended as a |# delimited section at the end of the metric, as so: metric.name:0|c|#tagName=val,tag2Name=val2 See Tags in the DogStatsD documentation for the concept description and Datagram Format. If you encounter problems, note that this tagging style is incompatible with the original statsd implementation. Be aware: If you mix tag styles (e.g., Librato/InfluxDB with DogStatsD), the exporter will consider this an error and the sample will be discarded. Also, tags without values (#some_tag) are not supported and will be ignored.
Located in LBN / … / Network Monitoring / BastionLinux 36
python3-ironic-prometheus-exporter-4.0.0-1.lbn36.noarch
ironic-prometheus-exporter provides a way to export hardware sensor data from ironic project in OpenStack to Prometheus. It's implemented as an oslo-messaging notification driver to get the sensor data and a Flask Application to export the metrics to Prometheus. It can be used not only in metal3 but in any OpenStack deployment which includes Ironic service.
Located in LBN / … / Cloud Computing / BastionLinux 36
python3-opentelemetry-exporter-prometheus-1.12.0rc1-1.lbn36.noarch
This library allows to export metrics data to Prometheus. Installation pip install opentelemetry-exporter-prometheus References OpenTelemetry Prometheus Exporter Prometheus OpenTelemetry Project
Located in LBN / … / Core Linux / BastionLinux 36
python3-prometheus-flask-exporter-0.20.3-1.lbn36.noarch
This library provides HTTP request metrics to export into Prometheus. It can also track method invocations using convenient functions. The following metrics are exported by default (unless the export_defaults is set to False). * flask_http_request_duration_seconds (Histogram) Labels: method, path and status. Flask HTTP request duration in seconds for all Flask requests. * flask_http_request_total (Counter) Labels: method and status. Total number of HTTP requests for all Flask requests. * flask_http_request_exceptions_total (Counter) Labels: method and status. Total number of uncaught exceptions when serving Flask requests. * flask_exporter_info (Gauge) Information about the Prometheus Flask exporter itself (e.g. version).
Located in LBN / … / Core Linux / BastionLinux 36

« Previous 10 items 1 2 3 4

Sections

Search results for prometheus exporter


	Copyright © 2000-2024 Corporation of Balclutha Inc. All rights reserved.