Personal tools
Skip to content. | Skip to navigation
iPerf3 exporter is configured via command-line flags. To view all available command-line flags, run iperf3_exporter -h. The timeout of each probe is automatically determined from the scrape_timeout in the Prometheus config. This can be also be limited by the iperf3.timeout command-line flag. If neither is specified, it defaults to 30 seconds. Prometheus Configuration The iPerf3 exporter needs to be passed the target as a parameter, this can be done with relabelling. Optional: pass the port that the target iperf3 server is lisenting on as the "port" parameter. Example config: scrape_configs: - job_name: 'iperf3' metrics_path: /probe static_configs: - targets: - foo.server - bar.server params: port: ['5201'] relabel_configs: - source_labels: [__address__] target_label: __param_target - source_labels: [__param_target] target_label: instance - target_label: __address__ replacement: 127.0.0.1:5201 # The iPerf3 exporter's real hostname:port.
Exporter for Celery/Flower metrics, inspired by https://github.com/vooydzig/flower-prometheus-exporter
A lightweight Go Web Server that receives POST alert messages from Prometheus Alert Manager and sends it to a Microsoft Teams Channel using an incoming webhook url. Synopsis Alertmanager doesn't support sending to Microsoft Teams out of the box. Fortunately, they allow you to use a generic webhook_config for cases like this.
The Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integration such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts.
Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.
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.
Features MongoDB Server Status metrics (cursors, operations, indexes, storage, etc) MongoDB Replica Set metrics (members, ping, replication lag, etc) MongoDB Replication Oplog metrics (size, length in time, etc) MongoDB Sharding metrics (shards, chunks, db/collections, balancer operations) MongoDB RocksDB storage-engine metrics (levels, compactions, cache usage, i/o rates, etc) MongoDB WiredTiger storage-engine metrics (cache, blockmanger, tickets, etc) MongoDB Top Metrics per collection (writeLock, readLock, query, etc*)
A Prometheus metrics exporter for LDAP. This exporter allows for configurable tree attributes to be exposed as prometheus metrics, and bundles a set of useful metrics for LDAP backends it knows of (currently this is just 389 Directory Server).