Observability Overview
Watasu’s observability is one Grafana per app, fed by three signals: logs, metrics, and traces. You attach the signals you want; Grafana shows up automatically the first time you do.
The four pieces
Section titled “The four pieces”| Add-on | What it gives you | Read more |
|---|---|---|
| Logs | Centralized log collection, queryable in Grafana | Logs |
| Metrics | Prometheus-style metrics scrape + queries + alerts | Metrics |
| Traces | Distributed tracing for request paths across services | Traces |
| Grafana | The shell — dashboards, exploration, alerting UI | This page |
Grafana shows up automatically
Section titled “Grafana shows up automatically”You don’t provision Grafana separately. The first time you attach a logs, metrics, or traces add-on to an app, Watasu creates a Grafana workspace for that app and wires the signal up as a data source.
That means a typical first observability step is:
watasu addons:create logs --app my-appwatasu addons:create metrics --app my-appwatasu addons:create traces --app my-appAfter the first one, Grafana exists. Each subsequent one adds a data source.
Persistence
Section titled “Persistence”Grafana is persistent. Dashboards, folders, alert rules, and saved explorations survive across restarts and releases. You don’t lose them by redeploying.
Access
Section titled “Access”Access to an app’s Grafana follows access to the app. People who can read the app can read the dashboards; people who can operate the app can edit dashboards and alerts.
When to use what
Section titled “When to use what”Each signal answers a different kind of question:
- Logs — what did the app actually print?
- Metrics — how much, how often, how fast, over time?
- Traces — where did this single slow request spend its time?
Most incidents touch all three: the alert fires from a metric, you check logs to see what’s failing, and you pull a trace to see where the slowness is.
App logs vs. Grafana logs
Section titled “App logs vs. Grafana logs”There are two log surfaces and they’re for different jobs:
watasu logs | Grafana logs | |
|---|---|---|
| Latency | Live tail | Indexed and queryable |
| Time window | Recent | Long retention |
| Filtering | Process | Labels, structured fields, full-text |
| Best for | Active debugging during a deploy | Historical search and dashboards |
Use watasu logs for “I just pushed and something’s wrong.” Use Grafana for “what was happening Tuesday at 3am?”