• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Paul S. · Oct 20, 2014 at 11:42 PM ·

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

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

4 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Paul S. · Nov 05, 2014 at 09:08 PM

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.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Oct 21, 2014 at 07:11 PM

Yes - this is odd. Maybe you want to open a ticket and discuss this with one of our support engineers

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Paul S. · Oct 21, 2014 at 01:50 AM

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. (sad)

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Oct 21, 2014 at 01:41 AM

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

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

1 Person is following this question.

avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A