The New Relic Prometheus OpenMetrics integration for Docker scrapes Prometheus endpoints and sends the data to New Relic. With this integration, you can:
- Automatically identify a static list of endpoints.
- Collect metrics that are important to your business.
- Query and visualize this data in the New Relic UI.
Reduce overhead, scale your data
The Prometheus OpenMetrics integration gathers all your data in one place, and New Relic stores the metrics from Prometheus. This integration helps remove the overhead of managing storage and availability of the Prometheus server.
Whether you're getting started with Prometheus or have been monitoring your environment along with a separate monitoring tool, New Relic can help. To learn more about how to scale your data without the hassles of managing Prometheus and a separate dashboard tool, see New Relic's Prometheus integration blog post.
New Relic has contributed the Prometheus integration to the open source community under an Apache 2.0 license. This integration supports Prometheus protocol version 2. The integration was tested using Docker 1.9, 1.11, and 1.13 on kops, GKE, and minikube.
The following limits apply:
- 50 attributes per metric.
- 50k unique timeseries. (A timeseries is a single, unique combination of a metric name and any tags or attributes.)
- 100k data points per minute. (If you need a higher limit, contact your New Relic account representative.)
Ready to get started? Here are some suggested next steps:
- Install the integration.
- Review the example configuration file and available options, including target configuration.
- Customize your Prometheus integration's configuration with New Relic as needed.
- Prevent unnecessary billing charges by filtering metrics sent to New Relic.
- To provide an additional level of security, use mutual TLS authentication.
- View and query your data in New Relic. Convert some common PromQL queries to NRQL queries.
- Visualize your data as charts, histograms and summaries, etc.
If you have problems with your integration, follow the troubleshooting procedures.