Skip to content
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

Metrics for job-controller #98434

Closed
alculquicondor opened this issue Jan 26, 2021 · 8 comments · Fixed by #101292
Closed

Metrics for job-controller #98434

alculquicondor opened this issue Jan 26, 2021 · 8 comments · Fixed by #101292
Assignees
Labels
area/workload-api/job kind/feature Categorizes issue or PR as related to a new feature. sig/apps Categorizes an issue or PR as relevant to SIG Apps. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@alculquicondor
Copy link
Member

alculquicondor commented Jan 26, 2021

What would you like to be added:

Metrics for the job controller operations, including:

  • latency of a job sync job_sync_duration_seconds
  • sync count job_sync_total (with a result label for success/error)
  • TBD job finished count job_finished_total (with a result label for success/error)

All metrics should include labels that allow to narrow delays or errors to features or code paths:

  • completion_mode: NonIndexed, Indexed.
  • TBD pattern: single, workQueue, fixedCompletion
  • TBD type of event that triggered sync, and whether it was immediate.

Why is this needed:

This is essential to diagnose common usage patterns or problems in the controller.

Note:

A KEP will be written for this feature, but we want to gather feedback on other useful metrics or labels. The lists are currently open to additions or removals.

/sig apps
/area workload-api/job

@alculquicondor alculquicondor added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 26, 2021
@k8s-ci-robot k8s-ci-robot added sig/apps Categorizes an issue or PR as relevant to SIG Apps. area/workload-api/job needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 26, 2021
@alculquicondor
Copy link
Member Author

cc @soltysh @ahg-g @erictune

@alculquicondor
Copy link
Member Author

cc @yangkev

@prydonius
Copy link

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 8, 2021
@alculquicondor
Copy link
Member Author

I've updated the job description to include the metric names and labels I propose.

The ones that are preceded with TBD I'm not convinced we need.

I'm wondering if a KEP is an overkill.

@ahg-g
Copy link
Member

ahg-g commented Mar 25, 2021

I feel the metrics are straightforward enough. Perhaps we add each metrics in a separate PR in which we discuss the exact semantics.

@alculquicondor
Copy link
Member Author

cc @AliceZhang2016

@AliceZhang2016
Copy link
Contributor

/assign

@alculquicondor
Copy link
Member Author

I'm documenting this in the KEP for beta graduation for indexed job kubernetes/enhancements#2616

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/workload-api/job kind/feature Categorizes issue or PR as related to a new feature. sig/apps Categorizes an issue or PR as relevant to SIG Apps. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants