From e7ef219f72f5261f955a862fa85fc9d4e3ba9146 Mon Sep 17 00:00:00 2001 From: Prathamesh Musale Date: Tue, 14 May 2024 09:38:26 +0530 Subject: [PATCH] Update instructions --- .../data/stacks/monitoring/monitoring-watchers.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/stack_orchestrator/data/stacks/monitoring/monitoring-watchers.md b/stack_orchestrator/data/stacks/monitoring/monitoring-watchers.md index dff8af9d..c4704f58 100644 --- a/stack_orchestrator/data/stacks/monitoring/monitoring-watchers.md +++ b/stack_orchestrator/data/stacks/monitoring/monitoring-watchers.md @@ -113,6 +113,12 @@ Add the following scrape configs to prometheus config file (`monitoring-watchers labels: instance: 'ajna' chain: 'filecoin' + + - job_name: graph-node + metrics_path: /metrics + scrape_interval: 30s + static_configs: + - targets: ['GRAPH_NODE_HOST:GRAPH_NODE_HOST_METRICS_PORT'] ``` Add scrape config as done above for any additional watcher to add it to the Watchers dashboard. @@ -131,7 +137,7 @@ Place the pre-configured alerts rules in Grafana provisioning directory: Update the alerting contact points config (`monitoring-watchers-deployment/config/monitoring/grafana/provisioning/alerting/contactpoints.yml`) with desired contact points -Add corresponding routes to the notification policies config (`monitoring-watchers-deployment/monitoring/grafana/provisioning/alerting/policies.yaml`) with appropriate object-matchers: +Add corresponding routes to the notification policies config (`monitoring-watchers-deployment/config/monitoring/grafana/provisioning/alerting/policies.yml`) with appropriate object-matchers: ```yml ...