Greetings All !
So, about two years ago, another developer decided to add Elastic APM to an existing ASP.NET (non-core) application. (Not sure what version of .NET it was on at the time, but we're on 4.7.2 right now.)
This has worked in a basic way for a while: We've been seeing page load data / tracing in Elastic just fine. And we've been capturing errors, but nobody has really looked at them.... until now....
I was asked to look into why we had several spikes in Errors being recorded in Elastic for this app for the past two months. I put quite a few hours into it. But other than determining that several of the spikes were being reported by a very small number of users.... or by PCs that have been dedicated as "wall monitors" that show the app... I really haven't been able to figure out much. All of the Exceptions are rather cryptic in what they report and their stack traces don't reveal much. OK, so the PageRequestManager reports a server request timed out... or that the status code returned (from.... something....) was 401....but I don't see any information about the request we were trying to make.
Or, another question / consideration that I have is: What if I switched this whole thing over to using the Public API? Would it still capture any errors from Microsoft's Ajax Script Library / Manager? (Right now, all C# errors are being written out to disk via log.net.)