I don’t have an ETA for this but I can assure you that customer requests are always looked at by the product manager when decisions on where to spend engineering time are made.
I think if you allow me to explain a little about our philosophy and what’s going on inside New Relic it might make more sense why this isn’t necessarily something that can be just slipped into Alerts. It actually goes back to how information about errors is collected by the agent monitoring your app.
When New Relic is collecting information about errors that are seen, we don’t instrument or trace every occurrence of every error. We’re trying to have a minimal impact on your application’s performance and so we collect a representative sampling of the errors seen. We’ll send up traces of some of these that you can view in the APM UI so that you can try and get a handle on what’s happening with your app. If we instrumented and traced every error then New Relic might wind up having a big impact on both application performance or even bandwidth usage in the event that a lot of errors occurred.
We have a similar philosophy for collection slow transaction traces. Most of the agents only collect a trace on the slowest transaction that ended in a given minute.
I hope this helps shed light on why alerting on every occurrence of a certain error code is not trivial. We’re not actually guaranteeing that we collect information about every single error seen. Since you can only alert off of data that is sent up to New Relic, if we’re collecting a representative sampling then you might miss a notification you’d expect.
This is why I’ve suggested a work around where you’re sending up a custom metric for the error code you see. You could also write a plugin that sends up every error code you see and alert based on a percentage of response codes being one you don’t want to see, or if you see one at all.
Please let me know if you’ve got more questions or if any of this doesn’t make sense. We want you to be able to get the relevant and timely notifications you need and sometimes the product doesn’t work or wasn’t designed to work in quite the way you’d like. I know that can be frustrating, especially when the reasoning behind why it behaves the way it does isn’t clear. Hopefully this clears things up some for you.