plone

prometheus-redis-exporter-1.74.0-0.1.git0096029.lbn36.x86_64
Prometheus Exporter for Redis Metrics. Supports ValKey and Redis 2.x, 3.x, 4.x, 5.x and 6.x
Located in LBN / … / DataBase / BastionLinux 36
prometheus-snmp-exporter-0.0.5-1.lbn19.noarch
See https://github.com/prometheus/snmp_exporter/blob/master/README.md for documentation.
Located in LBN / … / Big Data / BastionLinux 19
prometheus-snmp-exporter-0.20.0-1.lbn36.x86_64
This is an exporter that exposes information gathered from SNMP for use by the Prometheus monitoring system. There are two components. An exporter that does the actual scraping, and a generator (which depends on NetSNMP) that creates the configuration for use by the exporter.
Located in LBN / … / Network Monitoring / BastionLinux 36
prometheus-snmp-exporter-0.15.0-1.lbn25.x86_64
This is an exporter that exposes information gathered from SNMP for use by the Prometheus monitoring system. There are two components. An exporter that does the actual scraping, and a generator (which depends on NetSNMP) that creates the configuration for use by the exporter.
Located in LBN / … / Network Monitoring / BastionLinux 25
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
prosody-0.8.2-8.fc19.armv6hl
Prosody is a flexible communications server for Jabber/XMPP written in Lua. It aims to be easy to use, and light on resources. For developers it aims to be easy to extend and give a flexible system on which to rapidly develop added functionality, or prototype new protocols.
Located in LBN / … / VoIP / BastionLinux 19
prosody-0.8.2-11.fc19.x86_64
Prosody is a flexible communications server for Jabber/XMPP written in Lua. It aims to be easy to use, and light on resources. For developers it aims to be easy to extend and give a flexible system on which to rapidly develop added functionality, or prototype new protocols.
Located in LBN / … / VoIP / BastionLinux 19
protobuf-2.4.1-7.fc18.armv6hl
Protocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal RPC protocols and file formats. Protocol buffers are a flexible, efficient, automated mechanism for serializing structured data – think XML, but smaller, faster, and simpler. You define how you want your data to be structured once, then you can use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages. You can even update your data structure without breaking deployed programs that are compiled against the "old" format.
Located in LBN / … / Core Linux / BastionLinux 19
protobuf-2.4.1-2.lbn13.x86_64
Protocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal RPC protocols and file formats. Protocol buffers are a flexible, efficient, automated mechanism for serializing structured data – think XML, but smaller, faster, and simpler. You define how you want your data to be structured once, then you can use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages. You can even update your data structure without breaking deployed programs that are compiled against the "old" format.
Located in LBN / … / Zenoss 4 / BastionLinux 13

« Previous 10 items Next 10 items » 1 ... 2698 2699 2700 2701 2702 2703 2704 ... 4897

Sections

Search results


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