cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Skipped purepaths due to them being too old

nick_reese
Inactive

All. In a POC system I have started to get skipped PurePaths. Could anyone provide an insight into the log message?

2015-09-30 11:14:25 WARNING [com.dynatrace.diagnostics.server.datacenter.ac] Skipping a PurePath: EndUserRootPath[tag=7450139,action=EuActionNodeAttachment[name=_load_]] from realtime analysis and session storage because it is already too old. This PurePath will not be analyzed, as we cannot adapt measures that far in the past. PurePath creation time: Wed Sep 30 11:14:04 AEST 2015, start time: Sun Sep 27 18:25:26 AEST 2015, end time: Sun Sep 27 18:25:26 AEST 2015; PurePath: EndUserRootPath[tag=7450139,action=EuActionNodeAttachment[name=_load_]], isEndUser: true, isRIA: false. This message will be suppressed for the next 60s Suppressing this warning for another 60000 ms.

7 REPLIES 7

jason_ostroski
Dynatrace Pro
Dynatrace Pro

Nick,

If you take a look at your Dynatrace Server Health (Start Center->Deployment Health->Dynatrace Server Health) does anything spike high during the time that you are having issues? PurePath Buffer Size, RTA, CPU, Memory etc.

It looks like the PurePath was created 3 days after it ended and I wonder your PP Buffer isn't getting analyzed and written to disk.

Jason

nick_reese
Inactive

There doesn't appear to be anything maxing much - see screenshot. I'm wondering more about the timing anomaly.

andreas_grabner
Dynatrace Guru
Dynatrace Guru

I think what this means is that the Real Time Analyzer that is responsible to process PurePaths is not fast enough to process all PurePaths in time. The queue of PurePaths keeps filling up that it has to go through. When it gets to analyze a PurePath that has been sitting in the queue for too long it basically tells you "doesnt make sense to analzye this purepath as I cant book the measures any longer as the data has already been stored in our timeseries center". So - the problem I think you have is that the Real Time Analyzer sometimes cant cope up with the load. I would show this to our support folks - they have a lot of experience in optimizing dynatrace deployments. There are a lot of tweaks you can do to optimize e.g: number of real time analyzer threads being used

Andi

Hi Andreas,

In our System we are seeing Skipped purepaths with end time (year) 1970. Where is this end time coming from?

Thanks

Srikanth

Thats interesting. have never seen that before. Could be because of a glitch in our calculation when there are really skipped events which means there is missing time information on the purepaths. As I am not 100% sure you could open a support ticket in case this happens on a regular basis

Hi,

This problem suddenly occurred on September 9th, 2019 in our customers environment. The logs are followings. (The traffic and cpu, memory load was not high before and after this log was output. And Hardware and Software clock ware normal.)

2019-09-09 22:58:46 WARNING [RealTimeAnalysisQueue] Skipping a PurePath: <URL>#<AgentName>:21008(4d0e8536).1602742695 from realtime analysis and session storage because its start date is already too old. The PurePath exceeds the maximum PurePath age of 3600000ms. PurePath creation time: Mon Sep 09 22:58:25 JST 2019, start time: Mon Sep 09 22:58:29 JST 2019, end time: Thu Sep 26 12:39:25 JST 2019; PurePath: <URL>#<AgentName>:21008(4d0e8536).1602742695, isEndUser: false, isRIA: false, entry point virtual agent time: 1568037522888. This message will be suppressed for the next 60s Suppressing this warning for another 60000 ms.

2019-09-09 22:59:51 WARNING [RealTimeAnalysisQueue] Skipping a PurePath: <URL>#<AgentName2>:22676(8b31810d).1651329012 from realtime analysis and session storage because its start date is already too old. The PurePath exceeds the maximum PurePath age of 3600000ms. PurePath creation time: Mon Sep 09 22:59:29 JST 2019, start time: Mon Sep 09 22:59:33 JST 2019, end time: Sun Oct 13 02:21:24 JST 2019; PurePath: <URL>#<AgentName2>:22676(8b31810d).1651329012, isEndUser: false, isRIA: false, entry point virtual agent time: 1568037591778. This message will be suppressed for the next 60s Suppressing this warning for another 60000 ms.

Do you have any information? Why this problem was occurred? Has the FixPack for this problem been issued?


Best Regards,
Yasuo Ohnishi


nick_reese
Inactive

Thanks Andreas - much appreciated. At the moment the solution is only a POC and I it appears the client is pushing the available resources to their maximum. We are implementing a production quality solution in the next few weeks, so I will just keep a watching brief in the meantime.