One log viewer. Every source.
Deployments, builds, edge functions, and databases all stream into the same viewer — you learn one UI, filter once, and follow the tail while it happens.
4
Log sources
Deployment, build, edge, database
5,000
Lines per tail
100 · 200 · 500 · 1,000 · 5,000
3s
Live refresh
While resources build or run; 15s idle
0
Agents to install
Collected by the platform
What Observability is
Observability is where you see what your workloads are doing at runtime. Its core idea is one log viewer for many sources: deployments, builds, edge functions and managed databases all render in the same viewer and are queried through the same API, so you learn one interface instead of one per product.
The Overview page counts active sources, lists recent errors and flags anything currently building, each linking into a pre-filtered view. The Logs viewer filters by source, specific resource, severity and text, tails from 100 to 5,000 lines, refreshes every three seconds while things are active and follows the newest line.
Logs and events are deliberately separate. Logs are runtime stdout and stderr; events are control-plane actions such as create, deploy, fail and delete, shown on each resource's Activity tab. Every entry shares one schema with timestamp, severity, source, resource and message.
Logs are available organization-wide and inside each project, and any member can read them. Metrics, tracing, alerts and a unified audit view are the next surfaces on the roadmap.
Built for the moment something breaks
Source & resource filters
Filter by source, then pick a specific deployment, build, or edge version from live lists.
Severity chips
Color-coded info, warn, and error entries with a one-click severity filter.
Text search
Substring search across messages, combined with every other filter.
Auto-refresh & follow
Refreshes every 3s while resources are active and pins to the newest line.
Overview & recent errors
Per-source counts, recent errors, and a building badge, each deep-linking into a filtered view.
Copy & share
Copy the visible log text, or share a URL that keeps project, source, severity, and resource.
The same query, from your own tools
The dashboard talks to one Observability API. Query it per project or across the organization, or stream it over Server-Sent Events.
- Read-only for every organization member
- One canonical entry schema for every source
- Backed by Docker today, Loki when the stack is running
curl -G "$FLOWBIT_API/v1/organizations/$ORG_ID/projects/$PROJECT_ID/logs" \
--cookie "$FLOWBIT_SESSION" \
--data-urlencode "source=deployment" \
--data-urlencode "severity=error" \
--data-urlencode "tail=500" \
--data-urlencode "q=timeout"Everything the viewer can filter, the API can too
| Parameter | Values | Notes |
|---|---|---|
| source | deployment · build · edge · database | Omit to merge all project sources |
| ref | resource id | Drill into one resource |
| tail | 1 – 5000 | Default 200 lines per source |
| since | ISO 8601 | Native on Loki, best-effort otherwise |
| severity | debug · info · warn · error | Post-filter |
| q | text | Message substring search |
Where Observability is going
| Surface | Status | Scope |
|---|---|---|
| Overview | Live | Source stats, recent errors, deep links |
| Logs | Live | Org-wide and per-project viewer |
| Metrics | Phase 2 | Prometheus-backed charts |
| Tracing | Phase 2 | Distributed request traces |
| Alerts | Phase 2 | Rules and notifications |
| Audit | Phase 2 | Unified control-plane audit |
Common questions
What is the difference between logs and events?
Logs are runtime stdout/stderr. Events are control-plane actions — create, deploy, fail, delete — shown on each resource’s Activity tab.
Do I get Grafana access?
No. Grafana is an internal operations tool; you always use the flowbit viewer and API.
Are Cloud Shell sessions logged here?
Not as a source yet. Cloud Shell links to project and org logs until shell output becomes a first-class source.
How long are logs kept?
Retention policies are not enforced yet; long-term archive and export are on the roadmap.
See what production is doing
Built into every flowbit project — nothing to install.
Security & compliance
flowbit runs on independently audited security, privacy and cloud controls — so your apps and data meet the standards your customers expect.
