Monitoring

Statsd reporting

Zuul comes with support for the statsd protocol, when enabled and configured (see below), the Zuul scheduler will emit raw metrics to a statsd receiver which let you in turn generate nice graphics.

Configuration

Statsd support uses the statsd python module. Note that support is optional and Zuul will start without the statsd python module present.

Configuration is in the statsd section of zuul.conf.

Metrics

These metrics are emitted by the Zuul Scheduler:

zuul.event.<driver>.<type> (counter): Zuul will report counters for each type of event it receives from each of its configured drivers.

zuul.tenant.<tenant>.event_enqueue_processing_time (timer): A timer metric reporting the time from when the scheduler receives a trigger event from a driver until the corresponding item is enqueued in a pipeline. This measures the performance of the scheduler in dispatching events.

zuul.tenant.<tenant>.event_enqueue_time (timer): A timer metric reporting the time from when a trigger event was received from the remote system to when the corresponding item is enqueued in a pipeline. This includes zuul.tenant.<tenant>.event_enqueue_processing_time and any driver-specific pre-processing of the event.

zuul.tenant.<tenant>.management_events (gauge): The size of the tenant’s management event queue.

zuul.tenant.<tenant>.trigger_events (gauge): The size of the tenant’s trigger event queue.

zuul.tenant.<tenant>.pipeline

Holds metrics specific to jobs. This hierarchy includes:

zuul.tenant.<tenant>.pipeline.<pipeline name>

A set of metrics for each pipeline named as defined in the Zuul config.

zuul.tenant.<tenant>.pipeline.<pipeline name>.all_jobs (counter): Number of jobs triggered by the pipeline.

zuul.tenant.<tenant>.pipeline.<pipeline name>.current_changes (gauge): The number of items currently being processed by this pipeline.

zuul.tenant.<tenant>.pipeline.<pipeline name>.process (timer): The time taken to process the pipeline.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project

This hierarchy holds more specific metrics for each project participating in the pipeline.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>

The canonical hostname for the triggering project. Embedded . characters will be translated to _.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>.<project>

The name of the triggering project. Embedded / or . characters will be translated to _.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>.<project>.<branch>

The name of the triggering branch. Embedded / or . characters will be translated to _.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>.<project>.<branch>.job

Subtree detailing per-project job statistics:

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>.<project>.<branch>.job.<jobname>

The triggered job name.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>.<project>.<branch>.job.<jobname>.<result> (counter, timer): A counter for each type of result (e.g., SUCCESS or FAILURE, ERROR, etc.) for the job. If the result is SUCCESS or FAILURE, Zuul will additionally report the duration of the build as a timer.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>.<project>.<branch>.job.<jobname>.wait_time (timer): How long each item spent in the pipeline before its first job started.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>.<project>.<branch>.current_changes (gauge): The number of items of this project currently being processed by this pipeline.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>.<project>.<branch>.resident_time (timer): A timer metric reporting how long each item for this project has been in the pipeline.

zuul.tenant.<tenant>.pipeline.<pipeline name>.project.<canonical_hostname>.<project>.<branch>.total_changes (counter): The number of changes for this project processed by the pipeline since Zuul started.

zuul.tenant.<tenant>.pipeline.<pipeline name>.refresh (timer): The time taken to refresh the state from ZooKeeper.

zuul.tenant.<tenant>.pipeline.<pipeline name>.resident_time (timer): A timer metric reporting how long each item has been in the pipeline.

zuul.tenant.<tenant>.pipeline.<pipeline name>.total_changes (counter): The number of changes processed by the pipeline since Zuul started.

zuul.tenant.<tenant>.pipeline.<pipeline name>.trigger_events (gauge): The size of the pipeline’s trigger event queue.

zuul.tenant.<tenant>.pipeline.<pipeline name>.result_events (gauge): The size of the pipeline’s result event queue.

zuul.tenant.<tenant>.pipeline.<pipeline name>.management_events (gauge): The size of the pipeline’s management event queue.

zuul.executor.<executor>

Holds metrics emitted by individual executors. The <executor> component of the key will be replaced with the hostname of the executor.

zuul.executor.<executor>.merger.<result> (counter)

Incremented to represent the status of a Zuul executor’s merger operations. <result> can be either SUCCESS or FAILURE. A failed merge operation which would be accounted for as a FAILURE is what ends up being returned by Zuul as a MERGER_FAILURE.

zuul.executor.<executor>.builds (counter)

Incremented each time the executor starts a build.

zuul.executor.<executor>.starting_builds (gauge, timer)

The number of builds starting on this executor and a timer containing how long jobs were in this state. These are builds which have not yet begun their first pre-playbook.

The timer needs special thoughts when interpreting it because it aggregates all jobs. It can be useful when aggregating it over a longer period of time (maybe a day) where fast rising graphs could indicate e.g. IO problems of the machines the executors are running on. But it has to be noted that a rising graph also can indicate a higher usage of complex jobs using more required projects. Also comparing several executors might give insight if the graphs differ a lot from each other. Typically the jobs are equally distributed over all executors (in the same zone when using the zone feature) and as such the starting jobs timers (aggregated over a large enough interval) should not differ much.

zuul.executor.<executor>.running_builds (gauge)

The number of builds currently running on this executor. This includes starting builds.

zuul.executor.<executor>.paused_builds (gauge)

The number of currently paused builds on this executor.

zuul.executor.<executor>.phase

Subtree detailing per-phase execution statistics:

zuul.executor.<executor>.phase.<phase>

<phase> represents a phase in the execution of a job. This can be an internal phase (such as setup or cleanup) as well as job phases such as pre, run or post.

zuul.executor.<executor>.phase.<phase>.<result> (counter)

A counter for each type of result. These results do not, by themselves, determine the status of a build but are indicators of the exit status provided by Ansible for the execution of a particular phase.

Example of possible counters for each phase are: RESULT_NORMAL, RESULT_TIMED_OUT, RESULT_UNREACHABLE, RESULT_ABORTED.

zuul.executor.<executor>.load_average (gauge)

The one-minute load average of this executor, multiplied by 100.

zuul.executor.<executor>.pause (gauge)

Indicates if the executor is paused. 1 means paused else 0.

zuul.executor.<executor>.pct_used_ram (gauge)

The used RAM (excluding buffers and cache) on this executor, as a percentage multiplied by 100.

zuul.executor.<executor>.pct_used_ram_cgroup (gauge): The used RAM (excluding buffers and cache) on this executor allowed by the cgroup, as percentage multiplied by 100.

zuul.nodepool.requests

Holds metrics related to Zuul requests and responses from Nodepool.

States are one of:

requested
Node request submitted by Zuul to Nodepool

canceled
Node request was canceled by Zuul

failed
Nodepool failed to fulfill a node request

fulfilled
Nodes were assigned by Nodepool

zuul.nodepool.requests.<state> (timer)

Records the elapsed time from request to completion for states failed and fulfilled. For example, zuul.nodepool.request.fulfilled.mean will give the average time for all fulfilled requests within each statsd flush interval.

A lower value for fulfilled requests is better. Ideally, there will be no failed requests.

zuul.nodepool.requests.<state>.total (counter): Incremented when nodes are assigned or removed as described in the states above.

zuul.nodepool.requests.<state>.size.<size> (counter, timer)

Increments for the node count of each request. For example, a request for 3 nodes would use the key zuul.nodepool.requests.requested.size.3; fulfillment of 3 node requests can be tracked with zuul.nodepool.requests.fulfilled.size.3.

The timer is implemented for fulfilled and failed requests. For example, the timer zuul.nodepool.requests.failed.size.3.mean gives the average time of 3-node failed requests within the statsd flush interval. A lower value for fulfilled requests is better. Ideally, there will be no failed requests.

zuul.nodepool.requests.<state>.label.<label> (counter, timer)

Increments for the label of each request. For example, requests for centos7 nodes could be tracked with zuul.nodepool.requests.requested.centos7.

The timer is implemented for fulfilled and failed requests. For example, the timer zuul.nodepool.requests.fulfilled.label.centos7.mean gives the average time of centos7 fulfilled requests within the statsd flush interval. A lower value for fulfilled requests is better. Ideally, there will be no failed requests.

zuul.nodepool.requests.current_requests (gauge): The number of outstanding nodepool requests from Zuul. Ideally this will be at zero, meaning all requests are fulfilled. Persistently high values indicate more testing node resources would be helpful.

zuul.nodepool.requests.tenant.<tenant>.current_requests (gauge): The number of outstanding nodepool requests from Zuul drilled down by <tenant>. If a tenant for a node request cannot be determed, it is reported as unknown. This relates to zuul.nodepool.current_requests.

zuul.nodepool.requests.resources

Holds metrics about resource usage by tenant or project if resources of nodes are reported by nodepool.

zuul.nodepool.requests.resources.tenant

Holds resource usage metrics by tenant.

zuul.nodepool.requests.resources.tenant.<tenant>.<resource> (counter, gauge): Counter with the summed usage by tenant as <resource> seconds and gauge with the currently used resources by tenant.

zuul.nodepool.requests.resources.project

Holds resource usage metrics by project.

zuul.nodepool.requests.resources.project.<project>.<resource> (counter, gauge): Counter with the summed usage by project as <resource> seconds and gauge with the currently used resources by project.

zuul.mergers

Holds metrics related to Zuul mergers.

zuul.mergers.online (gauge): The number of Zuul merger processes online.

zuul.mergers.jobs_running (gauge): The number of merge jobs running.

zuul.mergers.jobs_queued (gauge): The number of merge jobs waiting for a merger. This should ideally be zero; persistent higher values indicate more merger resources would be useful.

zuul.executors

Holds metrics related to unzoned executors.

This is a copy of zuul.executors.unzoned. It does not include information about zoned executors.

Warning

The metrics at this location are deprecated and will be removed in a future version. Please begin using zuul.executors.unzoned instead.

zuul.executors.online (gauge): The number of Zuul executor processes online.

zuul.executors.accepting (gauge): The number of Zuul executor processes accepting new jobs.

zuul.executors.jobs_running (gauge): The number of executor jobs running.

zuul.executors.jobs_queued (gauge): The number of jobs allocated nodes, but queued waiting for an executor to run on. This should ideally be at zero; persistent higher values indicate more executor resources would be useful.

zuul.executors.unzoned

Holds metrics related to unzoned executors.

zuul.executors.unzoned.online (gauge): The number of unzoned Zuul executor processes online.

zuul.executors.unzoned.accepting (gauge): The number of unzoned Zuul executor processes accepting new jobs.

zuul.executors.unzoned.jobs_running (gauge): The number of unzoned executor jobs running.

zuul.executors.unzoned.jobs_queued (gauge): The number of jobs allocated nodes, but queued waiting for an unzoned executor to run on. This should ideally be at zero; persistent higher values indicate more executor resources would be useful.

zuul.executors.zone

Holds metrics related to zoned executors.

zuul.executors.zone.<zone>.online (gauge): The number of Zuul executor processes online in this zone.

zuul.executors.zone.<zone>.accepting (gauge): The number of Zuul executor processes accepting new jobs in this zone.

zuul.executors.zone.<zone>.jobs_running (gauge): The number of executor jobs running in this zone.

zuul.executors.zone.<zone>.jobs_queued (gauge): The number of jobs allocated nodes, but queued waiting for an executor in this zone to run on. This should ideally be at zero; persistent higher values indicate more executor resources would be useful.

zuul.scheduler

Holds metrics related to the Zuul scheduler.

zuul.scheduler.eventqueues

Holds metrics about the event queue lengths in the Zuul scheduler.

zuul.scheduler.eventqueues.management (gauge): The size of the current reconfiguration event queue.

zuul.scheduler.eventqueues.connection.<connection-name> (gauge): The size of the current connection event queue.

zuul.scheduler.time_query (timer): Each time the scheduler performs a query against the SQL database in order to determine an estimated time for a job, it emits this timer of the duration of the query. Note this is a performance metric of how long the SQL query takes; it is not the estimated time value itself.

As an example, given a job named myjob in mytenant triggered by a change to myproject on the master branch in the gate pipeline which took 40 seconds to build, the Zuul scheduler will emit the following statsd events:

zuul.tenant.mytenant.pipeline.gate.project.example_com.myproject.master.job.myjob.SUCCESS +1

zuul.tenant.mytenant.pipeline.gate.project.example_com.myproject.master.job.myjob.SUCCESS 40 seconds

zuul.tenant.mytenant.pipeline.gate.all_jobs +1

Prometheus monitoring

Zuul comes with support to start a prometheus metric server to be added as prometheus’s target.

Configuration

To enable the service, set the prometheus_port in a service section of zuul.conf. For example setting scheduler.prometheus_port to 9091 starts a HTTP server to expose metrics to a prometheus services at: http://scheduler:9091/metrics

Metrics

These metrics are exposed by default:

process_virtual_memory_bytes (gauge)

process_resident_memory_bytes (gauge)

process_open_fds (gauge)

process_start_time_seconds (gauge)

process_cpu_seconds_total (counter)

Liveness Probes

The Prometheus server also supports liveness and ready probes at the following URIS:

//health/live: Returns 200 as long as the process is running.

//health/ready: Returns 200 if the process is in RUNNING or PAUSED states. Otherwise, returns 503. Note that 503 is returned for INITIALIZED, so this may be used to determine when a component has completely finished loading configuration.

//health/status: This always returns 200, but includes the component status as the text body of the response.