Metrics
Crossplane produces Prometheus style metrics for effective monitoring and alerting in your environment. These metrics are essential for helping to identify and resolve potential issues. This page offers explanations of all these metrics gathered from Crossplane. Understanding these metrics helps you maintain the health and performance of your resources. Please note that this document focuses on Crossplane specific metrics and doesn’t cover standard Go metrics.
To enable the export of metrics it’s necessary to configure the --set metrics.enabled=true option in the helm chart.
These Prometheus annotations expose the metrics:
| Metric Name | Description | Further Explanation |
|---|---|---|
| Total number of certificate read errors | |
| Total number of certificate reads | |
| Histogram of RunFunctionResponse latency (seconds) | |
| Number of used workers per controller | The number of threads processing jobs from the work queue. |
| Maximum number of concurrent reconciles per controller | Describes how reconciles can happen in parallel. |
| Total number of reconciliation errors per controller | A counter that counts reconcile errors. Sharp or non stop rising of this metric might be a problem. |
| Length of time per reconciliation per controller | |
| Total number of reconciliations per controller | |
| Histogram of the latency of processing admission requests | |
| Current number of admission requests served | |
| Total number of admission requests by HTTP status code | |
| Number of HTTP requests, partitioned by status code, method, and host | |
| Total number of adds handled by workqueue | |
| Current depth of workqueue | |
| The number of seconds has the longest running processor for workqueue been running | |
| How long in seconds an item stays in workqueue before requested | The time it takes from the moment a job enter the workqueue until the processing of this job starts. |
| Total number of retries handled by workqueue | |
| The number of seconds of work done that’s in progress and hasn’t observed by work_duration. Large values means stuck threads. | |
| How long in seconds processing an item from workqueue takes | The time it takes from the moment the job start until it finish (either successfully or with an error). |
| The number of managed resources that exist | |
| The number of managed resources in Ready=True state | |
| The number of managed resources in Synced=True state | |
| Measures in seconds how long it takes a Cloud SDK call to complete | |
| The number of external API calls | The number of calls to cloud providers, with labels describing the endpoints resources. |
| Measures in seconds how long the reconciles for a resource delay from the configured poll periods | |
| The time it took to delete a managed resource | |
| The time it took for a managed resource to become ready first time after creation | |
| The time it took to detect a managed resource by the controller | |
| Measures in seconds the time-to-readiness (TTR) for managed resources |