Add CICD metrics

[christophe-kamphaus-jemmic]

Fixes #1600

Changes

This PR adds metrics for CICD systems and related attributes.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions. → NA

[carlosalberto]

Overall LGTM. A small (non-blocking) question: were cicd.pipeline.run.queued and cicd.pipeline.run.active considered as a single metric, with a state or similar label? Not proposing that, just curious on whether that was considered, as they are very similar.

[christophe-kamphaus-jemmic]

Overall LGTM. A small (non-blocking) question: were cicd.pipeline.run.queued and cicd.pipeline.run.active considered as a single metric, with a state or similar label? Not proposing that, just curious on whether that was considered, as they are very similar.

No I did not consider it until now. It's only with the latest changes that the similarity between these two metrics became apparent.
Also the cicd.pipeline.run.duration and cicd.pipeline.run.time_in_queue seem very similar.

I'm open to combine these two metric pairs and distinguishing them with phase attribute if additional reviewers are in favor of this change.

[lmolkova]

Overall LGTM. A small (non-blocking) question: were cicd.pipeline.run.queued and cicd.pipeline.run.active considered as a single metric, with a state or similar label? Not proposing that, just curious on whether that was considered, as they are very similar.

Not a strong opinion, but I like the idea of merging cicd.pipeline.run.queued and cicd.pipeline.run.active to something like cicd.pipeline.run.count with cicd.pipeline.run.state attribute.

Also the cicd.pipeline.run.duration and cicd.pipeline.run.time_in_queue seem very similar.

I don't think those are similar to cicd.pipeline.run.queued|active

• these metrics could easily have different range (different order of magnitude) of values (e.g. time in queue is hopefully tiny and pipeline duration is measured in minutes or hours)
• you'd configure different alerts for them and different people would pay attention to their values (in my BigCo anecdotal experience, workers are managed by a separate team/org and I have little control over them, while pipeline and its duration is controlled by dev teams)

[christophe-kamphaus-jemmic]

I have combined cicd.pipeline.run.active and cicd.pipeline.run.queued into cicd.pipeline.run.active distinguishing them with the cicd.pipeline.run.state attribute in 1d88f59.