Avoid sending Prometheus OpenMetrics integration data that is not relevant to your monitoring needs. Instead, use filters to ignore or include specific metrics. This will help you control the amount and types of data you send to New Relic. This will also help you avoid additional billing charges, as explained in this document.
Prevent billing increases
We use the Prometheus
scrape annotations. If you set the Prometheus OpenMetrics integration to scrape all the available targets and to send all the data that's exposed from those targets, you may exceed New Relic's platform limits and increase your billing charges. To help prevent this from happening, use the integration's filtering capabilities.
For more information, see the Prometheus OpenMetrics integration requirements for Docker. Also see the troubleshooting procedures for
Identify metrics to ignore or include
To decide what data to include or exclude, use New Relic's Metric API to explore your metric data. Then, refine your filters to scrape only relevant targets and send useful metrics.
- To filter out unwanted metrics from a target, use the
- To filter out targets instead of the metrics, use the
The histogram and summary metrics type filtering apply to the
base name. You can't filter by the
_count timeseries for that metric.
nri-prometheus-latest.yaml manifest file includes the
nri-prometheus-cfg config map showing an example configuration. The integration will ignore or include metrics before executing the other functions to add, rename, or copy attributes.