How to organize the monitoring of the CI job s in Networks?

Hello!
Faced with the case you want to track execution time of the job s in Networks.
Required to analyze the work as part of the service, whether there are drawdowns in the work that affect the execution of a task. And I want the dimension from the time spent with the developers, how much time the developer spends waiting for the task completion CI.
Fumbled on the net but some specifics have not found a similar question on the forum of Galaba https://forum.gitlab.com/t/monitoring-ci-metrics-b... But would like to know other options/practices.

While thinking to pull metrics run-time from the DB, but it looks a little spike.
April 3rd 20 at 17:25
2 answers
April 3rd 20 at 17:27
Solution
We decided to try it here is the solution. - networks-ci-pipelines-exporter
April 3rd 20 at 17:29
As rightly said @smilingcheater, is API.
If too lazy to write the monitoring, look at https://docs.gitlab.com/ee/administration/monitori...
https://docs.gitlab.com/omnibus/settings/grafana.html

Find more questions by tags GitContinuous integrationGitLab