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

Cumulative metrics for job/pipeline durations #778

Open
slsyy opened this issue Jan 19, 2024 · 3 comments
Open

Cumulative metrics for job/pipeline durations #778

slsyy opened this issue Jan 19, 2024 · 3 comments

Comments

@slsyy
Copy link

slsyy commented Jan 19, 2024

Right now we have only gitlab_ci_pipeline_job_duration_seconds or similar metrics, which cannot be used to answer questions like this:

  • how 95th percentile of particular job duration changes over time
  • what is the average duration of all pipelines over time

, because most of metrics returns data only for the latest job/pipeline.

Do you think that adding metrics such as histogram of durations will be consistent with the idea of the project and bring some added value?

@wnobres-sr
Copy link

wnobres-sr commented Jan 31, 2024

I'm looking for the same possibility actually so we can properly track the impact of improvements or identify decrease of performance of the jobs overtime. Is there a way to achieve that using the existing implementation or would require development effort?

@slsyy
Copy link
Author

slsyy commented Feb 6, 2024

Is there a way to achieve that using the existing implementation or would require development effort?

I don't think so. Current metrics keep only status for the last run. I will try to implement this kind of metrics to see, if it makes sense. Please inform me, if you are working on something similar or you have an alternative solution

@cgill27
Copy link

cgill27 commented May 14, 2024

Agree this would be good data to either collect or some way to pull it together in Grafana.
Would love to be able to set thresholds and alerts in Grafana to notify when there's an obvious problem across all pipelines/jobs etc.

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

No branches or pull requests

3 participants