-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide last_terminated_reason_timestamp for when last_terminated_reason event happens in K8s Integration #3802
Comments
I imagine that the accuracy of this value will be hard to pinpoint, but even an approx time would be great ... from looking at the data, it's useful to know if an error (such as OOMKilled) happened 7 mins or 7 hours or 7 days ago. |
I just tried using that field (elastic/beats#37192), and unfortunately, they seem to come in different events, leading to separate Metricbeat entries :( We need to look at any other potential fields or have Metricbeat somehow generate it for us. It looks like there's a request in the kubernetes repo to log the event whenever there's an OOMKilled: kubernetes/kubernetes#69676 |
Checking the existent metrics:
=> there is no such metric at the moment that would provide the time that last_terminated_reason of cotainer occurred What is needed:What is the interest of this issue is a
|
Here is a PR to report |
Progress:
|
Describe the enhancement:
Provide the
time
that last_terminated_reason of cotainer occurred in Kubernetes IntegrationPossible fields that can support that (from KSM-Pod metrics) can be kube_pod_status_container_ready_time.
Describe a specific use case for the enhancement or feature:
The "kubernetes.container.status.last_terminated_reason" is a useful field, especially in the case of missed metrics. This metric on its own can be difficult to identify when it happened as the container or pod can keep this error since last restart and also can be
This request is specifically for a timestamp for when this last_terminated_reason occurred.
What is the definition of done?
The text was updated successfully, but these errors were encountered: