Skip to content

Commit

Permalink
docs: discovery config link in readme
Browse files Browse the repository at this point in the history
  • Loading branch information
v-rocheleau committed Sep 18, 2024
1 parent f36e5ee commit f59582e
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,7 @@ that make up the Bento platform.
* [Troubleshooting guide](./docs/troubleshooting.md)
* [Deployment](./docs/deployment.md)
* [Monitoring](./docs/monitoring.md)
* [Public discovery configuration](./docs/public_discovery.md)

### Data ingestion and usage

Expand Down
5 changes: 3 additions & 2 deletions docs/monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Create the Grafana OIDC client, its permissions and group mappings with the foll
./bentoctl.bash init-auth
```

Set the outputed value for `BENTO_GRAFANA_CLIENT_SECRET` in the `local.env` file and restart Grafana.
Set the outputted value for `BENTO_GRAFANA_CLIENT_SECRET` in the `local.env` file and restart Grafana.

```bash
./bentoctl.bash restart grafana
Expand All @@ -57,7 +57,8 @@ Group role-mappings in Keycloak:
- Viewer
- Can view created dashboards

The `admin`, `editor` and `viewer` roles are Grafana concepts. During authentication, Grafana will synchronize the user's roles from Keycloak, and only let the user in if a valid role can be retrieved from the ID token.
The `admin`, `editor` and `viewer` roles are Grafana concepts. During authentication, Grafana will synchronize the
user's roles from Keycloak, and only let the user in if a valid role can be retrieved from the ID token.

The `init-auth` step in the [configuration](#configuration) creates everything needed for this in Keycloak.

Expand Down

0 comments on commit f59582e

Please sign in to comment.