Meaningful metrics in CircleCI Enterprise
planned
L
Lighthouse
At the moment the metrics are very basic and don't provide a lot if insight into how CircleCI Enterprise is behaving at the user level.We would like to have the following metrics to be able to tune our installation to our user needs and build dashboards so the developer teams can monitor their workflows.- build lifecycle metrics: succeeded, failed, queued, paused, running builds count- build duration- filter by: repo name, job name and workflow name
CCI-I-917
S
Shenoda elmasry Global Maasr Chemical's
G
C
Cos
We should also have clear documentation of all the available metrics for CircleCI Server 3.x. I understand the available metrics are not documented currently.
Nathan Fish
planned
We intend to bring insights 2.0 API and UI, currently available in cloud to the server installation. If you haven't seen insights the following will give you some additional information on its usage and features https://circleci.com/docs/2.0/insights.
We will also be providing a Prometheus/Loki/Grafana stack which will provide health metrics and aggregated logs. This includes health and performance metrics for nomad clients.
Nathan Fish
under review
Nathan Fish
Merged in a post:
Additional Metrics in Server
E
Eugene Choe
Metrics for Operators in CircleCI Server, accessible via a metrics service. For example:
of requested builds: the number of builds that have been requested over a specific time frame.
of failed/successful builds: we currently have "dead" (Nomad parlance) which accounts for successful and failed builds, can this be split into failed and successful?
of CircleCI frontend accessed: the number of times The UI is accessed
of users: this is available through the UI and REPL, could this be exposed as a metric?
of projects: the number of projects building on CircleCI
of times GH/GHE apis were called from CircleCI
of times CircleCI APIs were called
of jobs each nomad client are executing: we have an aggregate metric returned for jobs running across the cluster. would it be feasible to split this out for each client?
CCI-I-1258
C
Cory Dolphin
Great idea. My team would definitely use this
A
Aaron Webber
Being able to track the status of one particular job or workflow would be very helpful!