sadanand48 opened a new pull request, #10278:
URL: https://github.com/apache/ozone/pull/10278
## What changes were proposed in this pull request?
While trying to start up a docker compose cluster with monitoring, I see
that grafana process terminates instantly
```
export COMPOSE_FILE=docker-compose.yaml:monitoring.yaml
docker compose up -d --scale datanode=3
```
Grafana logs:
```
panic: runtime error: invalid memory address or nil pointer dereference
[recovered, repanicked]
[signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0x6150894]
goroutine 1 [running]:
github.com/grafana/grafana/pkg/cmd/grafana-server/commands.RunServer.func2()
github.com/grafana/grafana/pkg/cmd/grafana-server/commands/cli.go:89
+0x110
panic({0x88673c0?, 0x12b14680?})
runtime/panic.go:783 +0x120
github.com/grafana/grafana/pkg/services/provisioning/dashboards.(*configReader).parseConfigs(0x4003106490,
{0xb52c2c0?, 0x40019b0040?})
```
Grafana crashed because the bundled provisioning YAML used an old schema
that current Grafana could not parse, so dashboard provisioning hit a null
pointer during startup.
The PR changes:
1. Dashboard provisioning: Rewrote dashboards.yml to apiVersion: 1 with a
providers block and options.path, replacing the legacy root-level list so
current Grafana can parse it without panicking at startup.
2. Datasource provisioning: Added apiVersion: 1 and camelCase fields (orgId,
isDefault, etc.) in datasources.yml so Prometheus is provisioned in the format
Grafana expects.
3. Image pin: Set grafana/grafana:11.4.0 in monitoring.yaml instead of
floating latest, so local/CI runs stay reproducible and don’t break when
Grafana releases change.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-15285
## How was this patch tested?
Manually spinning up docker compose and loading up grafana
<img width="1695" height="864" alt="Screenshot 2026-05-15 at 2 30 48 PM"
src="https://github.com/user-attachments/assets/1b4c7129-89cb-498e-a845-d3cbb80aca24";
/>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
