How to organize monitoring of CI jobs in GitLab?

Question

git

Hello!
Faced with a case - It is required to track the execution time of jobs in GitLab.
It is required to analyze the work as from the side of the service, whether there are drawdowns in work that affect the execution of the task. And they want analytics from the side of the time spent by developers, how much time the developer spends waiting for the completion of CI tasks.
I rummaged through the network but didn’t find any specifics, there was a similar question on the gitlab forum https://forum.gitlab.com/t/monitoring-ci-metrics-b... But I would like to know other options / practices.
While we are thinking about pulling runtime metrics from the database, but it looks a little crutch.

Answer 1

We decided to try this solution. - gitlab-ci-pipelines-exporter

Answer 2

As smilingcheater rightly said , there is an API.
If you are too lazy to write monitoring yourself, look at https://docs.gitlab.com/ee/administration/monitori...
https://docs.gitlab.com/omnibus/settings/grafana.html