Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Fix typo #102

Merged
merged 1 commit into from
Nov 3, 2024
Merged

chore: Fix typo #102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/graphcast/radios/subgraph-radio/monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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://<SUBGRAPH_RADIO_URL>:<SUBGRAPH_RADIO_GRAPHQL_PORT>/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://<SUBGRAPH_RADIO_URL>:<SUBGRAPH_RADIO_GRAPHQL_PORT>/api/v1/graphql`. You can learn more about the HTTP server in the next section.

### Reading the Grafana dashboard

Expand Down
Loading