mirror of
https://github.com/camptocamp/odoo-cloud-platform.git
synced 2026-10-22 21:51:57 +00:00
David Gallay
95f6a48b9d
The cron and the prometheus.metric table only existed to pass values from the cron process to the HTTP workers. Querying the database directly when /metrics is scraped removes the cron, the table and the staleness.
35 lines
1.1 KiB
ReStructuredText
35 lines
1.1 KiB
ReStructuredText
.. image:: https://img.shields.io/badge/licence-AGPL--3-blue.svg
|
|
:alt: License
|
|
|
|
==============================
|
|
Monitoring: Prometheus metrics
|
|
==============================
|
|
|
|
Add an endpoint */metrics* to allow a Prometheus server to fetch application metrics.
|
|
Current available metrics are:
|
|
|
|
* Request completion time with 3 differentiators:
|
|
* Filestore
|
|
* Assets
|
|
* Everything else
|
|
* Longpolling request count
|
|
|
|
No additional configuration is needed, just ensure that the Prometheus server is allowed to communicate with Odoo
|
|
|
|
Gathering metrics from the database
|
|
-----------------------------------
|
|
|
|
Metrics that require a database query are gathered on the fly by the */metrics*
|
|
endpoint, with ``sudo()`` since the endpoint is public, and published as gauges.
|
|
|
|
To publish new metrics, extend ``_gather_metrics`` on the ``prometheus.gatherer``
|
|
abstract model and return the result of ``super()`` extended with your own entries::
|
|
|
|
{
|
|
"name": "odoo_some_metric",
|
|
"documentation": "What this metric measures",
|
|
"labels": {"label_name": "label_value"},
|
|
"value": 42,
|
|
}
|
|
|