From 9047f7e2ab4bfd2ac9a50413a8d4986e2b36a4e4 Mon Sep 17 00:00:00 2001 From: i0n Date: Thu, 31 Oct 2024 12:42:12 +0000 Subject: [PATCH] chore: Fix typo --- docs/graphcast/radios/subgraph-radio/monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/graphcast/radios/subgraph-radio/monitoring.md b/docs/graphcast/radios/subgraph-radio/monitoring.md index 4abd9c96..c2de022f 100644 --- a/docs/graphcast/radios/subgraph-radio/monitoring.md +++ b/docs/graphcast/radios/subgraph-radio/monitoring.md @@ -30,7 +30,7 @@ The Subgraph Radio exposes metrics that can then be scraped by a Prometheus serv The Subgraph Radio Grafana dashboard is included by default in Stakesquid's docker-compose stack. If you're not using the stack, below is a walk-through of how you can set it up. -There is a [Grafana dashboard config JSON file](https://github.com/graphops/subgraph-radio/blob/dev/grafana.json) provided in the repo, which you can import and use to visualise the metrics in Grafana. When importing the dashboard, it will require you to specify two data sources - a Prometheus one and a GraphQL one. For Prometheus you should select the Prometheus instance that you've set up to scrape metrics from Subgraph Radio's metrics host and port. For GraphQL, you'd need to install the [Infinity data source plugin](https://grafana.com/docs/plugins/yesoreyeram-infinity-datasource/latest/), if you don't have it already installed. The dashboard is configured to point to the default Kubernetes service deployments for Subgraph Radtio using [Launchpad Namespaces](https://github.com/graphops/launchpad-namespaces) If you are deploying using a different configuration the dashboard endpoints will need to be adjusted on lines: 878, 890, 895 and 898. The format for these addresses is: `http://:/api/v1/graphql`. You can learn more about the HTTP server in the next section. +There is a [Grafana dashboard config JSON file](https://github.com/graphops/subgraph-radio/blob/dev/grafana.json) provided in the repo, which you can import and use to visualise the metrics in Grafana. When importing the dashboard, it will require you to specify two data sources - a Prometheus one and a GraphQL one. For Prometheus you should select the Prometheus instance that you've set up to scrape metrics from Subgraph Radio's metrics host and port. For GraphQL, you'd need to install the [Infinity data source plugin](https://grafana.com/docs/plugins/yesoreyeram-infinity-datasource/latest/), if you don't have it already installed. The dashboard is configured to point to the default Kubernetes service deployments for Subgraph Radio using [Launchpad Namespaces](https://github.com/graphops/launchpad-namespaces) If you are deploying using a different configuration the dashboard endpoints will need to be adjusted on lines: 878, 890, 895 and 898. The format for these addresses is: `http://:/api/v1/graphql`. You can learn more about the HTTP server in the next section. ### Reading the Grafana dashboard