04 Mar 2019 04:09 AM - last edited on 19 May 2021 03:21 AM by MaciejNeumann
We have asynchronous call to Splunk logging that is being executed in separate thread and not blocks main thread but this asynchronous call included in PurePath processing time.
How to exclude it? It is not quite right.
Or it is to support team? Did anyone noticed simular behaviour?
Thanks and regards, Igor
Same PurePath today looks absolutely correct - calls to Splunk go async and do not block main thread.
Why in 21 feb it was presented as at first pic?
I have code snippet to prove that all calls to Splunk go async and do not block main thread.
Whart is was 21 feb? How to explain it to customer?
Was it kind of visualization problem fixed in v1.162 update?
Are here any one from support to check 1.162 update PurePath related fixes?
How it looks on Purepaths Code Level (both examples) and on Method Hotspots in both scenarios? Are there any differences?
Code level for first PurePath already lost during its age. For another one i will be able to access system only in coming Monday. Thank you for suggestion Sebastian!