Incidents lose PurePaths, somebody an idea why? dynaTrace 6.0
Hello Guys,
I observed an interesting behavior, so incidents recorded by dynaTrace start to lose the purepaths. They are often empty. I created an Incident rule for transactions with a lot of DB Queries. The pure paths are where, but after a while they are simply gone if I drill in.
Somebody observed this? Now I have a lot of incidents and if I drill down, nothing is where. Even if in the source the host raised this event is still in the incident.
Measure is copied and split by source.
Thanks,
Paul
Response from app support:
The configured incident rule "High Number of SQL Queries" fires when the sum of all executed SQL statements (over all transactions) within a minute is above 500. The maximal number of executed SQL statements for a single transaction within the stored session is 62. Since no single PurePath / Transaction has more than 500 SQL statements, no PurePath is shown after the drill-down. For this incident the correct drill-down would be to show all PurePaths within the time frame of the incidents, since the total number of SQL statements of all the PurePaths violates the threshold. Based on the forum article, I think that's anyway not what the customer wants to have.
To get an incident if a transaction has more then X SQL statements please change the aggregation type in the incident rule from "sum" to "max". With this change also the drill-down should work and you should only see PurePaths with more than X SQL statements.
Yes - this is odd. Maybe you want to open a ticket and discuss this with one of our support engineers
storage should be fine. 12GB of memory (max setting) and a lot of hard disk.
I could check the Server Config to increase just the memory. As we use just 12GB of it. Well not sure if this would by something.
The transactions are now already empty minutes after the event occurs. 
Hi Paul
Incidents DO NOT store the PurePaths. An Incident only knows which measures triggered them. So - when you drill to the PurePath the drill down is actually to those PurePaths in that timeframe that contributed to these measures. In case you look at an older Incident where you do not have a PurePath anymore, e.g: because you dont have enough storage in your continuous session storage - then these PurePaths can no longer be shown.
I hope this makes sense. You should look into extending your storage. Typcial installations most often retain PurePaths for up to several weeks by giving the continuous sessoin storage enough disk space
