New Relic Prometheus Configurator (a.k.a. New Relic Prometheus Agent) gives you full observability of your services exposing Prometheus metrics.
This repo contains the code base of the newrelic-prometheus-configurator and the Helm Chart to install the solution in Kubernetes.
The newrelic-prometheus-configurator uses a custom configuration that simplifies the experience related to configure features like discovery, filtering, metrics decoration, and sharding.
flowchart LR
id1>NewRelic Config] --> Configurator
Configurator --> id2>Prometheus Config]
id2>Prometheus Config] --> id3(Prometheus Agent)
style id1 stroke:#333,stroke-width:2px
style id2 stroke:#333,stroke-width:2px
The Configurator generates a configuration file that is used to run a Prometheus Server in Agent mode, and send metrics to the New Relic Remote Write Endpoint.
You can install this chart using nri-bundle located in the
helm-charts repository or directly from this repository by adding this Helm repository:
helm repo add newrelic-prometheus https://newrelic.github.io/newrelic-prometheus-configurator
helm upgrade --install newrelic newrelic-prometheus/newrelic-prometheus-agent -f your-custom-values.yamlFor further information of the configuration needed for the chart just read the chart's README.
The simplest way to start working with this project is to install the Chart in your Kubernetes cluster.
All pods and endpoints with the newrelic.io/scrape: true annotation will be scraped by default.
Moreover, the solution will scrape as well all pods and endpoints with the prometheus.io/scrape: true annotations and
having one of the labels matching the integrations_filter configuration.
Notice that at any point you can turn off the integrations filters and scrape all pods and services annotated with
prometheus.io/scrape: true by setting config.kubernetes.integrations_filter.integrations_filter: false or turning
it off in any specific job.
For further information check out the official documentation and if you are migrating from nri-prometheus check the migration guide.
Dashboard:
You can import an already pre-constructed dashboard by importing the dashboard.json file. Note that for the import to work you need to replace the json placeholder ACCOUNT_ID_PLACEHOLDER for your New Relic accountID. You can use the following command to do so:
sed -i '' 's/ACCOUNT_ID_PLACEHOLDER/accountID/g' assets/dashboard.json
Golang is required to build the integration. We recommend the Golang version that is used by the go.mod file.
After cloning this repository, go to the directory and build it:
make buildIf you plan modify the code of the configurator, charts or tests we recommend you to run the local environment
To run it locally you can use CLI directly piping in, or setting the --input flag pointing to the New Relic configuration and the Prometheus configuration will be printed out:
./bin/prometheus-configurator --input=path/to/nr-configWe use minikube and Tilt to launch a local cluster and deploy the main chart and a set of testing endpoints from the test-resource.
Make sure you have these tools or install them:
A license key and cluster name are required to run the environment. Configure them by the environment variables NR_PROM_CLUSTER and NR_PROM_LICENSE_KEY.
Start the local environment:
export NR_PROM_CLUSTER=<cluster name>
export NR_PROM_LICENSE_KEY=<NewRelic ingest key>
make start-local-cluster
make tilt-upNotice that local images are build and pushed to docker running inside the minikube cluster since we are running eval $(minikube docker-env) before launching Tilt.
For more in depth details regarding importing dashboards, you can check the official docs.
make testDetailed info about integration tests here.
Make sure you have these tools or install them before running the tests:
Then run:
make chart-unit-testThis test is based on the newrelic-integration-e2e. This tool will start the local environment and check if the expected metrics have reached the New Relic platform.
export ACCOUNT_ID=<NewRelic account number>
export API_REST_KEY=<NewRelic api rest key>
export LICENSE_KEY=<NewRelic ingest key>
make start-local-cluster
make e2e-testThe newrelic-prometheus-configurator images are pushed to newrelic/newrelic-prometheus-configurator repo. The following tags are pushed:
maineach PR merged to the main branch will update this image.nightlyeach night this image will be updated with the latest changes in the main branch.latesteach Release will be update this image.- Release tag eg:
0.0.1 - Pre-Release tag eg:
0.0.1-pre
Automated Release:
This release uses the release toolkit in order to automatically compute the version, changelog and release notes from the ## Unreleased section for the Changelog.md and dependency bots commits.
To trigger this release run Configurator Release workflow. This workflow automatically calculates the version from the changelog and commits the new changelog to the main branch.
Release notes and new changelog can be previously checked by running the make release-changelog and make release-notes commands. Check Release Toolkit for more details.
Manual release of images: Is possible to manually trigger the build and push of a configurator image from any branch by executing the Actions->manualRelease->Run Workflow.
The chart is released thanks to helm/chart-releaser-action, the package is hosted in Github releases and the index in Github pages.
The release process uses the release toolkit in order to automatically compute the version, changelog and release notes from the ## Unreleased section for the chart Changelog.md and dependency bots commits.
Therefore, the chart version should not be changed manually in the Chart.yaml, since it is automatically bumped.
To trigger this release run Configurator Chart Release workflow. This workflow automatically calculates the version from the chart changelog and commits the new changelog and the version to the main branch.
Release notes and new changelog can be previously checked by running the make release-changelog-chart and make release-notes-chart commands. Check Release Toolkit for more details.
New Relic hosts and moderates an online forum where customers can interact with New Relic employees as well as other customers to get help and share best practices. Like all official New Relic open source projects, there's a related Community topic in the New Relic Explorers Hub. You can find this project's topic/threads here.
We encourage your contributions to improve Newrelic Prometheus Configurator! Keep in mind that when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project.
If you have any questions, or to execute our corporate CLA (which is required if your contribution is on behalf of a company), drop us an email at [email protected].
A note about vulnerabilities
As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.
If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.
If you would like to contribute to this project, review these guidelines.
To all contributors, we thank you! Without your contribution, this project would not be what it is today. We also host a community project page dedicated to Newrelic Prometheus Configurator(<LINK TO https://opensource.newrelic.com/projects/... PAGE>).
Newrelic Prometheus Configurator is licensed under the Apache 2.0 License.
The Newrelic Prometheus Configurator also uses source code from third-party libraries. You can find full details on which libraries are used and the terms under which they are licensed in the third-party notices document.