From a34418d338c775429c3405fdb80813fd5bbda2aa Mon Sep 17 00:00:00 2001 From: Jim Lin Date: Sat, 5 Sep 2026 17:42:25 +0800 Subject: [PATCH] feat(health): add the metricsDb service under infrascope Prometheus and Thanos are the metric persistence layer and had no service of their own. metrics stays collection and visualisation; influxdb and kapacitor stay under notifications for now, since kapacitor is a write proxy and alerting engine here, not only storage. Adds the service to the /services example and to the three service-name enums (health history x2, module repair). Signed-off-by: Jim Lin Co-authored-by: Eandalf Co-authored-by: Claude Opus 5 (1M context) --- docs.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs.yaml b/docs.yaml index 6f280ac..a40475a 100644 --- a/docs.yaml +++ b/docs.yaml @@ -423,6 +423,11 @@ paths: - name: monasca - name: telegraf - name: grafana + - name: metricsDb + category: infrascope + modules: + - name: prometheus + - name: thanos - name: logAnalytics category: infrascope modules: @@ -1574,6 +1579,7 @@ paths: - businessLogic - dataPipe - metrics + - metricsDb - logAnalytics - notifications description: The name of the service to retrieve health history. use GET /api/v1/datacenters/{dataCenter}/services @@ -1836,6 +1842,7 @@ paths: - businessLogic - dataPipe - metrics + - metricsDb - logAnalytics - notifications description: The name of the service to retrieve health history. use GET /api/v1/datacenters/{dataCenter}/services @@ -2044,6 +2051,7 @@ paths: - businessLogic - dataPipe - metrics + - metricsDb - logAnalytics - notifications description: The name of the service which cover the module you tend to repair.