Use New Relic's
NrIntegrationError event to understand problems related to data ingest, limits, and feature configuration.
NrIntegrationError event is used to capture issues related to:
- Exceeding of our data ingest limits
- Exceeding of our query limits
- Malformed data
- Configuration issues
You can run NRQL queries to analyze
NrIntegrationError error messages. You can also set up alerts to be notified when specific types of errors, or certain quantities of errors, occur.
NrIntegrationError events are primarily categorized by the feature that is sending them, as indicated by the
newRelicFeature attribute. Values include:
Metricsindicates an issue with Metric API ingest.
Event APIindicates an issue with Event API ingest.
Logsindicates an issue with logs ingest.
Distributed Tracingindicates an issue with distributed tracing (
For attribute definitions, see the data dictionary.
Here are some examples of queries:
If you want to examine the structure of this event and see what attributes are attached, you can use a
keyset() query, like this:
FROM NrIntegrationError SELECT keyset()
Here are links to docs that go into more detail about how to use
NrIntegrationError-related docs for our core ingest APIs.
NrIntegrationError events are generated not just for direct use of these APIs but for any New Relic tools that rely on those API endpoints for reporting data:
- Metric API: see Troubleshoot Metric API ingest
- Event API: see parsing errors and tips for troubleshooting event reporting.
- Log API: See No log data appears.
- Trace API: see Response validation and Troubleshoot missing data.
If you're interested in manipulating these events via API, see Programmatically use NrIntegrationError.
If you're trying to understand changes that have been made in your New Relic account (like when a user made a change), see