Errors APM Panel.. it's really terrible.!

I love the option to search for specific errors…It’s a great feature…


@Addis-Zemen.Tesfaye Awesome! Glad you like it.

Adding in my voice here – while I like the new errors panel for what it is (errors over time is very useful), I can’t stop using the old one. The key thing for me is scan-ability – I can see both the action and type and message all in one chart, and I can sort by time. With error analytics I cannot do that – I can group by various methods, but I still have to click each error to get the full readout of action, type, and message, which is often necessary for me to understand what’s going on and to quickly see if any new errors have cropped up recently that I haven’t seen before (which would indicate something new is going wrong).

Please think about increasing the ease of reading if you are indeed going to remove the old errors page. The new one, while useful, just is hard to read quickly.

Hey @jro - thanks for the thoughtful feedback! I’m glad you’re liking the capabilities of the new one as well. Could you let us know what’s missing for you in the Error traces table of Error analytics? It sounds like that’s where you’re feeling like you’d want to get a better summary. Is the issue the lack of grouping of the individual errors, or something else?

1 Like

Yeah, that’s a lot of it – I relied on the groupings to get an overview of the entire time period and to see what was cropping up. Traces doesn’t give me all the errors in the time period I’m looking at, and lack of grouping makes it very hard to parse.

Thanks for the additional comments, @jro! I’ve added your feedback for our product managers to review. It’s great to get these specific descriptions of what would be helpful to you.

@alexis: I have been looking at the new errors view and the associated information. I would request that the old errors view is not deprecated until the .Net agent has the same functionality as other agents.

As our estate runs on .Net, I am currently unable to utilise the full functionality so cannot provide feedback.

@stefan_garnham It definitely won’t be removed until .NET has full capability in the new experience as all the other agents. Thanks for the feedback!

1 Like

Please don’t deprecate the old error page regardless of agent capability.
Both error pages have their use.

The new one focuses on error frequency in detail, the old one on errors in general.

When we want to simply see “is there anything wrong?”, the old one is much easier to process at a glance without all the graph smog the new one provides.

The new one is also not small screen (notebook) friendly while on the move. I don’t have a 24" display in front of me all the time. The old one uses screen estate better.

1 Like

@frans That is a interesting way to put both of them to use! I can’t make any promises that we will keep the old page, but I will give your input to our Product Managers. Thank you for letting us know how you are using both pages!

I agree to Frans, the old painel is very easier and useful, and currently is the first reason i still using newrelic in our environment. The new painel for me dont needs exist… doesn’t help anything… i need a trainning to understand that and if i needs it for a log/errors painel definitely something is wrong.

Hi @eoliveira - it looks like we had previously worked with you in a ticket as well as in this post. The agent that you use, .NET, doesn’t yet have full functionality for the new panel. I’ve made sure your feedback is captured for our product managers so that we understand the need for full support from the .NET agent. As mentioned by @scarpenter above, the old panel will continue to be around until the .NET agent fully supports the new functionality at least.


Hello everyone - thank you so much for your feedback on the new errors page. We’ve released some improvements to the error analytics page incorporating the helpful input you gave us. We hope you’ll find the new view a better help in exploring and diagnosing your errors, and we welcome any more feedback you may have!

1 Like

Hi @alexis - Sorry but I don’t see this is much of an improvement. I am running the .Net agent only so it may not yet be as richly featured until it supports TransactionError events.

Hey @stefan_garnham - I see you also gave your feedback to @scarpenter in his post - thanks for reaching out so thoroughly! As he mentioned we are all excited for that support to arrive. :slight_smile:

Just an update - we added support for Error analytics to the .NET Agent today. Check out details here.


Hi, not sure if this is the right place, but I’d like to provide some feedback on the Error Analytics report, and impending retirement of the Errors report.

The new Error analytics report is powerful, and in combination with insights I can really dig into data, but for me the most basic and most important workflow is much harder.

Let me explain: We have a big python application that’s monitored by New Relic, and I check New Relic everyday to see whether there are any errors in the part that my team covers. This is really easy since all relevant urls/transactions/classes have a specific marker in the name (let’s say the classes are called xyz.function.subfunction). What I do is I go to the Errors page, type ‘xyz’ in the filter box and immediately see all relevant information.

Getting this same information from the Error Analytics page is incredibly hard! I can group by Transaction Name, but if there are 20 unimportant transactions (not all transactions are equally important) with more errors then the relevant transactions don’t show at all.
Additionally the search box does not allow me to just type ‘xyz’ and filter on the transaction names.

I like the more advanced features, but please do not retire the normal Errors page until the simple things work too.

Thank you

1 Like

Yea. The old erros page is so important for us. It would’t be replaced never. Its so basic but works so much well and maybe it works fine because that.

@scarpenter @SamusSam Any news on whether the old page will be kept?

The ‘Errors’ page still shows the warning that it will be deprecated, but the ‘Error Analytics’ page still does not support important workflows. I very much agree with @ Frans in that regard (see also my previous message): ‘Errors’ is superior for my most important workflow.