Observability Overview
How observability works on Convoy Cloud: where to find it, how access is granted, and what your workspace gets out of the box.
Every Convoy Cloud workspace ships with its own Grafana organization, pre-loaded with dashboards for the applications in that workspace. There is nothing to install, configure, or sync. This page describes where observability lives in the product, how access is granted, and what to expect when you open it.
Where to find it
Observability is in the main sidebar. Clicking it opens the Observability page, which is the entry point for all metrics and logs in your active workspace.
The page shows:
- The name of the Grafana workspace you are about to enter.
- Your role in that Grafana organization (Viewer or Editor), mapped from your Convoy Cloud role.
- An Open Grafana button.
- Quick-link cards for the most common views: Tenant overview, Application logs, and Resource usage.
Clicking any of these opens Grafana in a new tab. Convoy Cloud handles the sign-in handshake silently using your existing session, so you will not be prompted for credentials.
How access works
Access is provisioned automatically at every stage:
- When you create a workspace, the platform creates a matching Grafana organization and seeds the dashboards described in Grafana dashboards.
- When you sign up, the platform creates your Grafana user account.
- When you join a workspace, the platform adds you to that workspace's Grafana organization with the appropriate role.
- When you are removed from a workspace, the platform revokes your Grafana membership.
You never manage Grafana users or organizations directly. Manage your team in Members and the observability surface follows along.
Role mapping
| Convoy Cloud role | Grafana role |
|---|---|
| Admin | Editor |
| Member | Viewer |
Editors can save dashboard customisations and create panels. Viewers can read every dashboard but cannot save changes.
One Grafana organization per workspace
Each Convoy Cloud workspace is backed by exactly one Grafana organization. Metrics and logs are scoped to that workspace's Kubernetes namespace, so:
- You only see telemetry for applications in your own workspace.
- There is no path to query another workspace's data through your Grafana, even if you have an account there.
- If you belong to multiple workspaces, each is a separate Grafana organization.
Switching workspaces
Switch workspaces in the Convoy Cloud sidebar, then click Open Grafana again. Do not switch organizations from inside Grafana — that path is not part of the supported flow.
What you get out of the box
- Metrics from Prometheus, retained for 15 days, covering CPU, memory, network I/O, pod health, and restart counts.
- Logs from Loki, retained for 7 days, collected automatically from your application's stdout and stderr.
- Four pre-configured dashboards described in Grafana dashboards.
Retention windows are platform-wide and not tied to billing tier.
New-tab gateway
Grafana opens in a new browser tab. Convoy Cloud does not embed Grafana in an iframe. This keeps the SSO handshake clean and lets Grafana use its own session cookie. Closing the Grafana tab does not affect your Convoy Cloud session.
Direct access
The fallback URL is grafana.convoy-tech.com. It is supported but not the recommended path — you may need to sign in again, and you will land in the last organization you used, which may not match your active workspace. Use the Observability page in the sidebar for day-to-day access.