You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be the same as #119
I realized, that gitlab_ci_pipeline_time_since_last_run_seconds will not get updated for merge request pipelines, if the merge request was deleted. I expect, that this also happens with branch refs.
I can only provide a screenshot from a custom dashboard
It is sorted by ID, so the most recent is on top. The eternal branches develop and master shows the correct values, but the merge request refs shows the exact time it took from pipeline completion to merge/delete.
Maybe a timestamp instead of a duration is more reliable?
The text was updated successfully, but these errors were encountered:
👋 hey @krebs-GVL, indeed, this is something that I wanted to do for a while, I just pushed it as part of a broader metric naming update (26ddfe8). It will be part the next release. You will therefore be able to use time() - gitlab_ci_pipeline_timestamp to compute the value dynamically in prometheus.
Hi,
This may be the same as #119
I realized, that
gitlab_ci_pipeline_time_since_last_run_seconds
will not get updated for merge request pipelines, if the merge request was deleted. I expect, that this also happens with branch refs.I can only provide a screenshot from a custom dashboard
It is sorted by ID, so the most recent is on top. The eternal branches
develop
andmaster
shows the correct values, but the merge request refs shows the exact time it took from pipeline completion to merge/delete.Maybe a timestamp instead of a duration is more reliable?
The text was updated successfully, but these errors were encountered: