Operational telemetry
Operational telemetry is how your team runs Fontana day to day: search logs, trace errors, watch dashboards, and confirm services are up. Fontana centralises this at the platform layer so every workspace does not need its own observability stack.
Your operators use Grafana with Loki as the log store, either shared across environments or installed alongside your workspaces. Gatus records service health history for platform and workspace workloads.
What gets collected
Section titled “What gets collected”| Source | Examples | Typical use |
|---|---|---|
| Platform workloads | Flow, workflow engine, backend services | Application logs, errors, run lifecycle |
| Flow browser | UI errors and product telemetry | Front-end incidents and usage signals |
| Backend | Structured execution and console events | Server behaviour and log stream topics |
| Workflow engine | Run lifecycle, capacity samples | Pipeline performance and failures |
| Connectors | Connector job output | Ingress and egress troubleshooting |
| Node metrics | CPU, memory, load on the host | Capacity and saturation |
Signals from each workspace pass through your workspace observability ingress before export to the platform OTLP gateway, so tenancy boundaries stay intact.
Platform Grafana and Loki
Section titled “Platform Grafana and Loki”Each install stamps environment and tenant labels on every OTLP batch. Grafana dashboards and Explore filter on both dimensions so shared platform backends stay tenant-scoped.
| Property | Behavior |
|---|---|
| Remote path | Your deployment team configures remote OTLP and Grafana URLs in fontana.yaml |
| Local path | Optional local observability UI on your platform status hostname |
| WORM audit | Unchanged — security audit storage stays per workspace |
Example LogQL in Grafana Explore:
{fontana_environment="<environment>", fontana_tenant_id="<tenant>"}Your deployment team provisions the Fontana tenant logs home dashboard, Loki datasource, and bundled alert packs on platform deploy.
Grafana operator access
Section titled “Grafana operator access”- Cloud: Grafana URL from your platform operator credentials
- Self-hosted: status hostname observability path from your install documentation
- Credentials: from your platform Terraform output or operator credential store
Use the Environment and Tenant variables at the top of the home dashboard, or Explore with the LogQL pattern above.
Gatus service health
Section titled “Gatus service health”Gatus runs per workspace and records a health history page separate from Grafana log search. It probes core workspace services and backing databases, plus shared platform services your deployment routes to the host.
Gatus records availability and uptime for those endpoints. Your administrator can share the status page URL from your deployment credentials.
Authentication: the Gatus status page enforces HTTP basic auth. Credentials are generated at deploy time and stored in your workspace secrets. Your operator documentation lists browser console logins.
Operational logs vs WORM system of record
Section titled “Operational logs vs WORM system of record”Grafana and Loki are the operational search plane: fast log query, dashboards, and alerting during incidents. Security audit events may be mirrored into the same Loki store for operator search.
ImmuDB is the compliance system of record for platform security audit. Loki retention, compaction, or index rotation does not change the append-only WORM ledger. For diligence, cite ImmuDB integrity procedures and Immutable audit trail.
See Data retention for retention boundaries across workflow data, operational logs, and ImmuDB.