-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add support for InitContainer create/termination timestamps in Pod Metrics #2627
Comments
cc @CatherineF-dev |
@richabanker: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Hi, could you share some use cases of monitoring these short-lived containers? |
I'm not the original asker, but I also want to monitor the start time of init containers. In my case it's because we're using the new Kubernetes Sidecar containers https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/ which are implemented as long running init containers. I'm trying to monitor when each sidecar is started and how long it takes for it to become ready, but those metrics only exist for "normal" containers |
I see. We have added tag |
What would you like to be added:
Expose the init containers start/terminated timestamps
Why is this needed:
We are trying to monitor the container start latencies and observed that kube_pod_container_state_started and kube_pod_container_status_last_terminated_timestamp does not provide information on the init containers.
Describe the solution you'd like
Expose the epoch time stamps of the init-containers creation and termination events
Additional context
The text was updated successfully, but these errors were encountered: