Feature Idea: Attributing 400 errors to requesting APM not receiving APM

When there are 400 errors, by default these are reported as errors against the receiving APM which is rejecting them. We want to be able to alert against the requesting service.
We have been able to attribute them to parent.app (when distributed tracing is on), but that is a APM number which is tedious to use by humans. A translation such as parent.name would be ideal.
When generating a alert on 400 errors, I would like to at least report who the sender is, and ideally alert on 400 errors by the sender.

if there was a function to translate parent.app to a name, e.g. parentAppName(parent.app), then I could write
SELECT COUNT() from Transaction limit 1000 since 3 hours ago TIMESERIES 1 minute where appName Like ‘Odin%’ and error is True and httpResponseCode LIKE ‘4%%’ FACET parentAppName(parent.app )
or alert if a service is sending too many failing requests.
SELECT COUNT(
) from Transaction limit 1000 since 3 hours ago TIMESERIES 1 minute where parentAppName(parent.app ) Like “NameService%” and error is True and httpResponseCode LIKE ‘4%%’

  • Let us know which NRQL queries you have tried so far:
    SELECT COUNT(*) from Transaction limit 1000 since 3 hours ago TIMESERIES 1 minute where appName Like ‘Odin%’ and error is True and httpResponseCode LIKE ‘4%%’ FACET parent.app

Helpful Resources:


New Relic Edit

  • I want this too
  • I have more info to share (reply below)
  • I have a solution for this

0 voters

We take feature ideas seriously and our product managers review every one when plotting their roadmaps. However, there is no guarantee this feature will be implemented. This post ensures the idea is put on the table and discussed though. So please vote and share your extra details with our team.

Appreciate you being so detailed in outlining your issue and how it could be addressed. I have changed this topic to a Feature Idea and added a poll so that we can see the level of interest from other community members. Our product team has also been made aware.

1 Like

At last review this feature was not accepted to be added to the roadmap. This request has been closed.