🌐
Prometheus
prometheus.io › docs › prometheus › latest › getting_started
Getting started | Prometheus
You can also verify that Prometheus is serving metrics about itself by navigating to its metrics endpoint: localhost:9090/metrics
🌐
Medium
eytanmanor.medium.com › an-introduction-to-prometheus-a-tool-for-collecting-metrics-and-monitoring-services-12fcc3bdb5d6
An introduction to Prometheus — a tool for collecting metrics and monitoring services | by Eytan Manor | Medium
January 2, 2023 - Service Discovery — Pull a list ... an HTTP endpoint or from a file. If the Prometheus server is running on a Kubernetes cluster, it would usually pull this information from the Kubernetes API. Scraping — For each service in the list, send an HTTP GET /metrics request and ...
🌐
Last9
last9.io › blog › getting-started-with-prometheus-metrics-endpoints
Getting Started with Prometheus Metrics Endpoints | Last9
April 14, 2025 - Grasping how this endpoint works ... performance. A Prometheus metrics endpoint is an HTTP endpoint (usually /metrics) that exposes monitoring data in a format Prometheus can scrape....
🌐
Spring
docs.spring.io › spring-boot › api › rest › actuator › prometheus.html
Prometheus (prometheus) :: Spring Boot
The prometheus endpoint provides Spring Boot application’s metrics in the format required for scraping by a Prometheus server.
🌐
Netfoundry
netfoundry.io › core concepts › metrics › prometheus endpoint
Prometheus endpoint | NetFoundry Documentation
The controller can expose a /metrics endpoint that serves network metrics in the Prometheus text exposition format.
🌐
Reddit
reddit.com › r/devops › how does prometheus monitoring work?
r/devops on Reddit: How does prometheus monitoring work?
June 1, 2023 -

This is a pretty n00b question even though I'd consider myself a pretty experienced DevOps and site reliability engineer. I've setup New Relic on our EC2 servers and have a lot of serverless metrics going to NR from AWS. I've also built some custom metrics for New Relic.

We recently started using a new tech called Rockset which is pretty cool. It has an endpoint for metrics collection. This endpoint spits out some metrics data in a portable known format - OpenMetrics/prometheus. Cool I get that so far. However I'm looking through the NR documentation and it's talking about setting up Kubernetes clusters? And/or a NR agent? The agent moves the data? Why would I need a huge cluster? For moving a ton of telemetry data? It's my goal to visualize this data in New Relic.

Top answer
1 of 4
23
I'll try and break down the different components here. Prometheus itself is monitoring software. It runs as a long-running service that scrapes endpoints (which you configure as scrape targets) and stores the metrics in a time-series database. Those endpoints are expected to provide metrics in the format you have mentioned, which has become known as 'OpenMetrics' format. The OpenMetrics format started as just a Prometheus thing, but it's become popular enough that many other monitoring tools will happily also scrape or 'understand' OpenMetrics formatted metrics. Prometheus can run on pretty much anything, because it's a Go program it just runs as a single binary. That means you can run Prometheus as a Windows executable, a Linux container, or on Kubernetes as pods if you want, among others. But it's part of the CNCF ecosystem, so it's commonly associated with Kubernetes and it is very Kubernetes-friendly. You can easily deploy Prometheus to run on K8s, and it also has automatic service discovery that allows it to easily discover and monitor K8s workloads for you. But it doesn't need to run on K8s or monitor it, it's just well suited to that. I'm not familiar with New Relic, but from some quick googling it mentions it can integrate with Prometheus' remote_write feature. Remote write was a feature that was developed for Prometheus that allows it to scrape its endpoints, and then forward the data onto another service. This lets you use Prometheus for what its really good at - scraping endpoints - and then ship the data off to something like New Relic to act as a data warehouse or for visualising data. Prometheus can also run in what's called 'agent mode', which is where it doesn't actually store any metrics, but is used exclusively to scrape then forward metrics (using remote_write) to something like New Relic. So it acts as an 'agent' rather than the traditional heavyweight server mode where it stores data. It looks like New Relic have also developed a newer way to monitor Kubernetes clusters with what they are calling the 'New Relic Prometheus Agent'. From reading their docs, this is simply a thin wrapper around Prometheus in agent mode that is configured to forward metrics to New Relic out of the box. Hopefully that helps. I have contributed to the Prometheus project and used it for many years, so if you have any questions let me know.
2 of 4
10
Save yourself some money, visualize it in grafana. The way the Prometheus works, you have a server ( which actually is the client) which is configured to call all the endpoints it can discover. The real power in Prometheus is its Dynamic Discovery Framework that allow you to have a configuration that talks to other things that actually get the list of instances. It can be kubernetes, it can be AWS API, whatever. Once you have a configuration of targets that's dynamically populated, the client( server, the main thing ) reaches out to all the clients( actually the servers, also known as exporters) which just sit there listening for connections to expose data to. the main process collects the data under its data dir, and also has a rudimentary interface to allow query and expose config and state information.
🌐
Honeycomb
docs.honeycomb.io › integrations › metrics › prometheus
Send Metrics from Prometheus Clients - Honeycomb Docs
Here is a bare bones example of a configuration file configured to scrape prometheus metrics and send them to Honeycomb: receivers: prometheus: config: scrape_configs: - job_name: "prometheus" scrape_interval: 15s static_configs: - targets: ["0.0.0.0:9100"] # this is the endpoint to scrape exporters: otlp/metrics: endpoint: "api.honeycomb.io:443" # US instance #endpoint: "api.eu1.honeycomb.io:443" # EU instance headers: "x-honeycomb-team": "YOUR_API_KEY" "x-honeycomb-dataset": "DESTINATION_DATASET_NAME" service: pipelines: metrics: receivers: [prometheus] processors: [] exporters: [otlp/metrics]
Find elsewhere
🌐
GeeksforGeeks
geeksforgeeks.org › devops › what-is-prometheus-endpoint
What is Prometheus Endpoint - GeeksforGeeks
July 23, 2025 - Prometheus endpoints are HTTP interfaces offered by various applications and services that give metrics in a Prometheus-compatible manner. These endpoints use the OpenMetrics exposition format, ensuring interoperability with Prometheus monitoring.
🌐
Grafana
grafana.com › docs › grafana-cloud › send-data › metrics › metrics-prometheus
Prometheus metrics | Grafana Cloud documentation
When sending metrics from multiple Prometheus instances, you can use the external_labels parameter to label time series data with an instance identifier. Append any external_labels to the global section of your Prometheus configuration file. You can find the /api/prom/push URL, username, and password for your metrics endpoint by clicking on Details in the Prometheus card of the Cloud Portal:
🌐
Netdata
netdata.cloud › monitoring-101 › prometheus-monitoring
Prometheus Endpoint Monitoring | Netdata
Prometheus endpoints are HTTP interfaces exposed by various applications and services that provide metrics in a format consumable by Prometheus. These endpoints follow the OpenMetrics exposition format, which ensures compatibility with Prometheus ...
🌐
Prometheus
prometheus.io › docs › prometheus › latest › querying › api
HTTP API | Prometheus
Prometheus can be configured as a receiver for the OTLP Metrics protocol. This is not considered an efficient way of ingesting samples. Use it with caution for specific low-volume use cases. It is not suitable for replacing the ingestion via scraping. Enable the OTLP receiver by setting --web.enable-otlp-receiver. When enabled, the OTLP receiver endpoint is /api/v1/otlp/v1/metrics.
🌐
SentinelOne
sentinelone.com › blog › prometheus-metrics-by-example
Prometheus Metrics by Example: 5 Things You Can Learn | Scalyr
October 27, 2022 - Instead, what they do is to expose an endpoint that returns a payload with all the metrics available in the Prometheus format. Every certain amount of time—say, five minutes—Prometheus will consume this endpoint to collect data.
🌐
SigNoz
signoz.io › guides › how to set up and secure prometheus metrics endpoints
How to Set Up and Secure Prometheus Metrics Endpoints | SigNoz
August 1, 2024 - It collects and stores time-series ... A Prometheus metrics endpoint is a specific URL — typically /metrics — that exposes these measurements in a format Prometheus can scrape and understand....
🌐
Microsoft
thalesdocs.com › ctp › cm › 2.10 › admin › cm_admin › monitoring › metrics › index.html
Prometheus Metrics Endpoint
On your CipherTrust Manager, enable Prometheus metrics, either through a POST to the /v1/system/metrics/prometheus/enable endpoint, or with the ksctl metrics prometheus enable CLI command.
🌐
IBM
ibm.com › docs › en › was › 9.0.5
Displaying PMI metrics in Prometheus format with the ...
You can use the metrics.ear file to create a Prometheus endpoint for your WebSphere Application Server runtimes to display PMI metrics in Prometheus format.
🌐
Google Groups
groups.google.com › g › prometheus-users › c › VRlVT9pV6Ss
How does Prometheus monitor HTTP/S endpoints.
If you just want to check if an endpoint is up you should use the blackbox exporter. If you want metrics from an application you should have Prometheus scrape it.
🌐
Galaxy
training.galaxyproject.org › training-material › news › 2023 › 01 › 24 › prometheus.html
New Feature: Prometheus Metrics endpoint
December 19, 2024 - Prometheus is an increasingly popular monitoring solution whereby sites expose a /metrics endpoint, and then a central Prometheus server can scrape it for data which is then plotted or visualised or alerted upon.
🌐
AWS
docs.aws.amazon.com › amazon managed service for prometheus › user guide › ingest metrics to your amazon managed service for prometheus workspace › ingest metrics with aws managed collectors › what are prometheus-compatible metrics?
What are Prometheus-compatible metrics? - Amazon Managed Service for Prometheus
To scrape Prometheus metrics from your applications and infrastructure for use in Amazon Managed Service for Prometheus, they must instrument and expose Prometheus-compatible metrics from Prometheus-compatible /metrics endpoints. You can implement your own metrics, but you don't have to.
🌐
Prometheus
prometheus.io › docs › introduction › first_steps
First steps with Prometheus | Prometheus
You can also verify that Prometheus is serving metrics about itself by navigating to its own metrics endpoint: http://localhost:9090/metrics .