Exceptions and Capturing the extended data behind it
we capturing the exception class, message, throwing class and throwing method. My question is we frequently add extended data to our exceptions. Is there a way to expose this in dynatrace? Meaning they are putting user Id and/or OrgId whenever a exception is being thrown. It helps them troubleshoot the problem much easier. If there another way of getting to this information, we would appreciate that too. If this isn't already been done, then please inform if a RE is needed.
hi Mark,
in general this would be a very nice RFE, i agree.
however, there is a potential technical problem that comes to my mind:
at what time do you set this exception data?
we collect exceptions by instrumenting the exception constructors. if we don't have this information available at that time, we don't have a chance to collect it with our current approach. so i guess this would not work for you, right?
best,
Christian
Mark. When you say you add data to your exception - how is that done? Is it a custom Exception class that contains members that contain that information? Would it be possible to also add this contextual information to the error message itself?
Actually, we are capturing the exception. We are also seeing the message, but I think they put additional information with the exception occurs that helps them to remediate the issue. So I didn't see it on a error dashlet. Another thing, when I go into the purepath, I was able to create a measure and chart it, but when I tried to build a Business Transaction for it, it wasn't capturing any data for it. Here an example of of denied login. What I'm saying is that they have more information or details around that exception which allows them to which Org the user was trying to access. In the Purepath for this exception the Argument is "BS0142".
Throwing Class:
XXXXXXXXX.XXX.Security.Authentication
Throwing Method:
Authenticate
Exception Class:
XXXXXXXXX.XXX.Security.SecurityLoginDeniedException
Message:
BS0142
Hi Mark
Seems like multiple questions - lets see how I can address them all:
a) The Errors Dashlet shows Errors based on the Error Rules you have configured in your System Profile. Some Exceptions will show up as errors as well as there are some out-of-the-box rules for it. Your exceptions may not yet show up as you need a specific rule for it to also let dynaTrace identify them as Errors. Once you do that you should see your exceptions as well in the Errors dashlet. Clicking on such an error should then show the Exception including the Message value which will contain your OrgValue
b) The Exception Dashlet shows ALL Exceptions that have been identified by dynaTrace - not just those that are also identified as Errors through the Error Rules. Here you should always see all of your exceptions including the Error Message
c) Not every measure can be used for Business Transactions. Depending on the type of BT (Server-Side, Page Action or Visit) you have a different set of PurePath Measures available to use for Filter, Result Value or Splitting. What type of measure did you want to use for your BT?
For BTs I recommend checking out the recently updated documentation "Usage of Business Transactions" and the Recorded Webinar "dynaLearn Webinar - Business Transaction Management - February 2, 2012"
Andi
What I’m after is having visibility to the additional info that can be added to an Exception class. This is done via a key/value collection under exception called data.
http://msdn.microsoft.com/en-us/library/system.exception.data.aspx
For example if I right mouse and hit details on an exception, possibly show a section for Additional Info if available…
Aaaah - now I get it - thanks for the link.
So - right now there is no support for the Data Collection. I will forward this to the engineering team as I think that this is a great extension to our exception sensor.
