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
I'm encountering an issue with the container_cpu_usage_seconds_total metric, where it occasionally spikes to very high values, such as 1.73 billion, for some containers. These values seem unusually large and only occur sporadically. After a short time, the metric returns to its expected range.
Details:
Metric: container_cpu_usage_seconds_total
Example of high value: ~1.73 Billion
Occurrence: Happens infrequently but returns to normal after some time
Frequency: Once in a while
Expected behavior: The metric should show the CPU usage in seconds, and these spikes seem abnormal.
Questions:
What might be causing these sporadic spikes in the metric?
Could this be an issue with the metric collection or reporting system?
Are there any recommended steps to debug or prevent this from happening?
Any help or insights would be greatly appreciated!
Thank you in advance for your time and assistance.
Best regards,
Roshni
The text was updated successfully, but these errors were encountered:
roshini-cp
changed the title
Insistent container_cpu_usage_seconds_total Shows Extremely High Values (e.g., 1.73 Billion)
Inconsistent container_cpu_usage_seconds_total Shows Extremely High Values (e.g., 1.73 Billion)
Oct 22, 2024
Hello team,
I'm encountering an issue with the container_cpu_usage_seconds_total metric, where it occasionally spikes to very high values, such as 1.73 billion, for some containers. These values seem unusually large and only occur sporadically. After a short time, the metric returns to its expected range.
Details:
Metric: container_cpu_usage_seconds_total
Example of high value: ~1.73 Billion
Occurrence: Happens infrequently but returns to normal after some time
Frequency: Once in a while
Expected behavior: The metric should show the CPU usage in seconds, and these spikes seem abnormal.
Questions:
What might be causing these sporadic spikes in the metric?
Could this be an issue with the metric collection or reporting system?
Are there any recommended steps to debug or prevent this from happening?
Any help or insights would be greatly appreciated!
Thank you in advance for your time and assistance.
Best regards,
Roshni
The text was updated successfully, but these errors were encountered: