Hello,
A picture tells a thousand words:
I have seen this on different environments and different managed clusters. Every time the xx:02, what is dynatrace trying to communicate here?
KR Henk
Solved! Go to Solution.
I'm looking into this!
@henk_stobbe I believe you run a version < 1.234. It has been already fixed. See release notes:
https://www.dynatrace.com/support/help/whats-new/release-notes/managed/sprint-234
and find a bug entry:
"User sessions" list filter dates are now parsed more precisely. (APM-339528)
1.232.108.20220127-121913