You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the bug?
This code is where the 'MetricsPurgeActivity' scans the PA metric location (defaulting to /dev/shm/performanceanalyzer/) and deletes all the files with last modified time greater than (referenceTime - purgeInterval). We have seen cases where the event log files keep lingering beyond the 60s window and it happens because 'MetricsPurgeActivity' is run as other collectors and is muted as per this recent code if the collector is taking longer to complete the execution.
What is the expected behavior?
Even log files should be cleaned after 60s time window
The text was updated successfully, but these errors were encountered:
What is the bug?
This code is where the 'MetricsPurgeActivity' scans the PA metric location (defaulting to /dev/shm/performanceanalyzer/) and deletes all the files with last modified time greater than (referenceTime - purgeInterval). We have seen cases where the event log files keep lingering beyond the 60s window and it happens because 'MetricsPurgeActivity' is run as other collectors and is muted as per this recent code if the collector is taking longer to complete the execution.
What is the expected behavior?
Even log files should be cleaned after 60s time window
The text was updated successfully, but these errors were encountered: