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.
Answer by Andreas G. ·
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
Answer by Nick R. ·
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.
Visits Split by Email 2 Answers
Support for CodeName one 1 Answer
UEM signal from static page 5 Answers