Grafana
Dashboards for the plant, built over the data your other apps already keep.
Category: Monitoring
Grafana is the dashboard and visualization tool from Grafana Labs. The App Store runs Grafana 13.2.3 in a single pod with its own persistent volume, on x86-64 and ARM64 nodes.
What it does
- Builds dashboards, panels, and variables over time-series and log data, from process trends to infrastructure health.
- Reads the App Store's own Grafana Loki, Prometheus, and InfluxDB apps as datasources.
- Keeps its users, dashboards, and alert state on the app's own volume, so they survive restarts and upgrades.
When to use it
Deploy Grafana when the live metric cards in EmberCORE aren't enough: historical trends, correlated signals, OEE, or any custom view of data your apps write. If you also want log aggregation on the same node, Grafana Loki runs Grafana and Loki together as one app.
Running on EmberNet
- It needs app subdomains. Grafana only works at its own app address, not through EmberCORE's built-in proxy, because a Grafana login does not hold through the proxy. Its interface opens inside EmberCORE from that address. If your EmberCORE deployment has no app subdomains, the App Store says so before you install it, and the app tells you why it cannot open instead of opening broken.
- An admin password made for this install. The app generates the password
for the
adminuser when it installs and keeps the same one across upgrades. It is stored in the Kubernetes Secret<release>-adminin your organization's namespace. Grafana only takes that password on a new database, so change it in Grafana afterwards. - No anonymous access. Everyone who opens Grafana signs in to it.
- One instance per node. Grafana keeps its database on a ReadWriteOnce volume (2 GiB by default), so it runs as a single replica.
- Locked down. It runs as an unprivileged user with a read-only root filesystem and no added capabilities.
Datasources
The app can wire up Loki, Prometheus, and InfluxDB datasources for you at install, pointed at the App Store's own apps by naming their release. Each one is off by default. An App Store deploy leaves all three off, so after a store deploy add the datasources in Grafana, using the address of the app you want to read:
| Datasource | Address |
|---|---|
| Loki, from the Grafana Loki app | http://<release>-loki:3100 |
| Prometheus | http://<release>:9090 |
| InfluxDB (InfluxDB 2, Flux) | http://<release>:8086, with the token from that app's Secret <release>-auth, key admin-token |
<release> is the name the App Store gave that app on its node. These short
addresses work when the app is in the same namespace as Grafana, which is the
case for apps your organization deployed.