This resource contains information about common errors and error messages that may alert you to issues with data visibility and availability, as well as information about how to respond.
If you receive an integration error message from New Relic or error messages in your Prometheus server logs after restarting your Prometheus server, there are several actions you can take to troubleshoot and get data flowing properly. Below are a few tips regarding common issues and error messages. For specific information on how to query for
NrIntegrationError events, see Investigate error messages below.
You can investigate error messages in New Relic by doing either or both of the following.
NrIntegrationErrorquery on the error message using NRQL, then look at the Message field in the UI to see a description of what went wrong. For example:SELECT * FROM NrIntegrationError WHERE newRelicFeature = 'Metrics'
Investigate individual errors in time to see when and where they occur and any simultaneously occurring issues, and perform targeted troubleshooting based on what you find out. For example:SELECT count(*) FROM NrIntegrationError WHERE newRelicFeature = 'Metrics' TIMESERIES
If you’ve validated that you can send data successfully but are unable to query it, you may be running into other kinds of limits, like the inspected count limit. This may manifest itself as an error message during the integration process that says:
Unable to retrieve data for Prometheus data source <name>.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.