GitHub
github.com › catawiki › json_exporter
GitHub - catawiki/json_exporter: Prometheus JSON REST API exporter · GitHub
This Prometheus exporter can be used to export metrics from a REST HTTP(S) API that provides JSON documents.
Starred by 39 users
Forked by 16 users
Languages: Python 96.3% | Dockerfile 2.0% | Earthly 1.7%
Starred by 18 users
Forked by 6 users
Languages: Go 95.5% | JavaScript 3.9%
Using Prometheus to ingest from foreign APIs
Write your own exporter (there are Prometheus client libraries for various languages) that queries the API and exposes its data in the Prometheus format: https://prometheus.io/docs/instrumenting/clientlibs/ https://prometheus.io/docs/instrumenting/writing_exporters/ More on reddit.com
Getting volume capacity utilization data from API
Have you configured OnCommand Unified Manager, this will do alerting based on capacity utilisation with different threshold levels. It is also pretty good with custom reports/graphs that can be scheduled to email these outputs to a list of email addresses. OCUM is included with your base bundle available from the NetApp software download page. Alternatively you can use the API to create your own outputs, I've done this in the past with powershell, NetApp WorkFlow Automation tool can provide powershell output examples.. More on reddit.com
Running multiple exporters = multiples process, ports, ... ?
in general this is the case. As far as configuration management, yeah you’ll sort of need to deal with that somehow. Here’s one reason you don’t necessarily want just one super-exporter. It would mean all your metrics are in a single basket and failure of you super exporter might lead to signal failure across many services. You don’t usually want that. You want to limit your blast radius as it were, in case of exporter failure, need for restarts due to config changes, etc. On our docker nodes, we do exactly what the other commenter posted, we reverse proxy lots of exporters through a traefik reverse proxy using url path to determine which exporter to proxy. When traefik goes down or restarts, we have a momentary metrics drop-out for the whole node, but we sort of accept it. In k8s, we have separate Ingress per exporter specifically to avoid that problem. More on reddit.com
Prometheus web exporter
How does this compare to https://github.com/prometheus/blackbox_exporter? I know the latter can also do web monitoring, so what's the overlap in features and what's unique to this new one?
More on reddit.comGoogle Groups
groups.google.com › g › prometheus-developers › c › qW527MN_7uQ
REST API exporter
The best method isn't to write an exporter, but rather to directly instrument the application to expose the needed metrics. What language is your application written in? ... Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message ... For my scenario, it's Java-based. I'll reach out to the developers to see if they are open to the idea of adding a Prometheus metrics endpoint.
Medium
medium.com › teamzerolabs › write-aprometheus-api-exporter-in-record-time-7518ee22f238
Write a Prometheus API Exporter in Record Time | by Jack Yeh | TeamZeroLabs | Medium
November 8, 2020 - Setup Prometheus to scrape these exporters for samples. Over time, Prometheus will build up Time Series for samples collected. Setup Grafana to visualize the data within Prometheus. … And more! (Alerting on thresholds, and refining types of measurement as time goes on) Next, we will go over the steps for creating an API exporter.
Google Groups
groups.google.com › g › prometheus-users › c › ORZ0t2ffuCA
How to connect a simple REST API to Prometheus
Hi Shutima A very easy way is to use https://github.com/prometheus/blackbox_exporter > The blackbox exporter allows blackbox probing of endpoints over HTTP, HTTPS, DNS, TCP and ICMP. We included lots of RESTful APIs in our blackbox config best regards Evelyn
Prometheus
prometheus.io › docs › prometheus › latest › querying › api
HTTP API | Prometheus
curl 'http://localhost:9090/api/v1/targets?scrapePool=node_exporter'
DEV Community
dev.to › erwanlt › monitoring-your-rest-api-with-prometheus-and-grafana-23dp
Monitoring your REST api with Prometheus and Grafana - DEV Community
February 1, 2022 - Else you need a running API, you can do that with these 2 options : ... And then, pull then using the command line. Normally you should see something like this in your docker CLI. You can directly run Grafana in a container, but Prometheus will need further configuration. Firstly to export our API metric, we need to add some new dependencies to the pom.xml
Prometheus
prometheus.io › docs › instrumenting › exporters
Exporters and integrations | Prometheus
There are a number of libraries and servers which help in exporting existing metrics from third-party systems as Prometheus metrics.
Starred by 26 users
Forked by 3 users
Languages: Python 97.4% | Dockerfile 2.6%
Medium
medium.com › @virendrasingr81 › monitoring-http-rest-api-in-kubernetes-using-grafana-prometheus-and-blackbox-exporter-1193c604cb69
Monitoring HTTP/REST API in Kubernetes using Grafana, Prometheus and Blackbox Exporter | by virendrasing rajput | Medium
December 26, 2023 - additionalScrapeConfigs: - job_name: 'blackbox-external-targets' metrics_path: /probe params: module: [http_2xx] static_configs: - targets: - http://www.google.com relabel_configs: - source_labels: [__address__] target_label: __param_target - source_labels: [__param_target] target_label: instance - target_label: __address__ replacement: prometheus-blackbox-prometheus-blackbox-exporter:9115
OneUptime
oneuptime.com › home › blog › how to build custom exporters for prometheus
How to Build Custom Exporters for Prometheus
December 5, 2025 - Custom exporters bridge this gap by translating metrics from various sources into Prometheus format. This guide shows you how to build exporters in Go and Python. graph LR subgraph External System DB[(Database)] API[REST API] LOG[Log Files] end subgraph Custom Exporter C[Collector] M[Metrics Registry] H[HTTP Server] end P[Prometheus] DB --> C API --> C LOG --> C C --> M M --> H H --> P
Reddit
reddit.com › r/prometheusmonitoring › using prometheus to ingest from foreign apis
r/PrometheusMonitoring on Reddit: Using Prometheus to ingest from foreign APIs
February 3, 2020 -
Greetings
I'm very new to Prometheus so I come here for pointers from the community.
My goal is to monitor a hardware device which exposes a nice REST API that contains all the data but not formatted specifically for monitoring.
What is the best approach/tool to have Prometheus "read" the data through this API?
Thanks in advance
Top answer 1 of 3
7
Write your own exporter (there are Prometheus client libraries for various languages) that queries the API and exposes its data in the Prometheus format: https://prometheus.io/docs/instrumenting/clientlibs/ https://prometheus.io/docs/instrumenting/writing_exporters/
2 of 3
2
As others have said, look at writing your own exporter to translate the API to a prometheus format. Best bet is to look at other exporters in a language you are comfortable with and copy them.
GitHub
github.com › mikejoh › exporter-example
GitHub - mikejoh/exporter-example: Example of how to write a Prometheus Exporter in Go · GitHub
This is an example of how to write a Prometheus Exporter in Go. In this example we'll explore how to write an exporter using Go and a simple service that exposes a REST API. The service API can be seen as an third party application that exposes some kind of data (of it's internal state) that could be exposed to Prometheus.
Author: mikejoh