Skip to content

validate_workload: detect OOMKilled and excessive#1241

Open
xinWeiWei24 wants to merge 1 commit into
v2from
xinwei/check_restart_oom
Open

validate_workload: detect OOMKilled and excessive#1241
xinWeiWei24 wants to merge 1 commit into
v2from
xinwei/check_restart_oom

Conversation

@xinWeiWei24

Copy link
Copy Markdown
Collaborator

No description provided.

# resource status, then scans the full container logs of its pods for error
# patterns. Requires kubectl on the agent and a kubeconfig already in place
# (e.g. via GetCredentials).
# resource status, then inspects each pod's live status for OOMKilled

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am thinking if it is a good idea to do this in prometheus with kube_pod_container_status_restarts_total metric Leonard had a PR for prometheus extension https://github.com/Azure/telescope/pull/1237/changes#diff-62ff5b9ce16ceffb2a778a23f876e84ed90e3970c4d2bedc177fb6bc417e89ed , will this still fit your use case?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the suggestion. I’d prefer to keep this test lightweight and avoid adding Prometheus or other extra load. I’m looking for a simpler validation method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants