Grafana
A dashboard the agent can point at its own data, instead of a STATUS.md it writes by hand.
- app
- observability
Run it
briq_run({
recipe: "grafana",
params: {
"size": "small",
"diskGb": 1
},
wait: true
})curl -X POST https://api.briq.cloud/v1/briqs \
-H "Authorization: Bearer $BRIQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"recipe": "grafana",
"params": {
"size": "small",
"diskGb": 1
},
"wait": true
}'
# → { "briqs": [{ "id": "bq_…", … }], "outputs": { "GRAFANA_URL": "…" }, … }
# ... when done, for each briq id
curl -X DELETE https://api.briq.cloud/v1/briqs/<id> \
-H "Authorization: Bearer $BRIQ_API_KEY"Parameters
| Name | Type | Options | Default |
|---|---|---|---|
| size | enum | nano, small, medium | "small" |
| diskGb | number | — | 1 |
Outputs
Returned by briq_run once the stack is healthy. Hosts resolve inside your team network; secrets are generated per run.
- GRAFANA_URL
- http://grafana.<stack>.internal:3000
- GRAFANA_ADMIN_USER
- admin
- GRAFANA_ADMIN_PASSWORD
- <GRAFANA_ADMIN_PASSWORD>
What it runs
| Briq | Image | Ports | Size | Volume |
|---|---|---|---|---|
| grafana | grafana/grafana:latest | 3000 | small | 1 GB at /var/lib/grafana |
When to use it
- The agent reports a load test or a long run as a paragraph of numbers, and you would rather see a chart.
- You want dashboards over data the agent's briqs already produce: Postgres, a Prometheus endpoint, logs.
- You want to hand someone a live dashboard instead of a note that goes stale.
Tips
- Wire it from the API:
POST /api/datasourcesonGRAFANA_URLwith basic auth (GRAFANA_ADMIN_USER,GRAFANA_ADMIN_PASSWORD). - Data sources in the same stack stay private; only Grafana needs a URL.
- Dashboards as JSON:
POST /api/dashboards/dbbeats building panels by hand. - Share it:
briq_run({ recipe: "grafana", expose: "private" }), orbriq_exposeport 3000 withmode: "private". - More room: the volume starts small; pass
diskGbfor more. Set it when the briq is created, and it counts toward your plan's disk.