Skip to main content

Reports

Observability → Reports answers questions about the whole project in one place, from the controller's /api/v3/reports endpoints. Every report exports to CSV or JSON (CSV files carry a BOM and are guarded against formula injection), and every resource name links to its resource.

The configuration and change reports are shown to project owners and admins; other roles see the fleet report. When the control plane has not built any report yet, the page says so instead of showing empty tables.

Problems​

Everything that needs a look, worst first, in one list: configuration a proxy rejected, failed or stuck jobs, offline and outdated clients, ACME and GSLB trouble, broken references, expiring certificates, domain conflicts and configuration hygiene (for example routes without a retry policy or clusters without outlier detection). Each problem has a severity — critical, error, warning or info — the resource it is about, since when it holds, and a suggested fix. Filter by severity or kind, or search.

Problems report — everything that needs a look, worst first Problems report — everything that needs a look, worst first

Traffic map​

Which listener serves which domain, and where each route sends it: listener → domain → route → cluster → endpoint, with ports and TLS. Shown as a tree (Map) or a flat Table, grouped by listener or by domain. The filters — listener, host, cluster, endpoint, port — are kept in the URL, so a filtered view can be shared. Type a host such as api.example.com to see only the virtual host that answers it.

Traffic map report — listeners, domains, routes, clusters and endpoints Traffic map report — listeners, domains, routes, clusters and endpoints

Security​

Per HTTP filter chain: whether it has TLS, a WAF (elchi-shield or Coraza), a local rate limit and authentication filters, and the certificates to renew. The counters on top show the chains without each protection.

Security report — TLS, WAF, rate limit and auth per filter chain Security report — TLS, WAF, rate limit and auth per filter chain

Fleet​

Every service of the project: where it runs, how many proxies are connected, its version, when it last synced and its active configuration errors. Counters for live, partial, offline and not deployed services.

Fleet report — services, proxies, versions and configuration errors Fleet report — services, proxies, versions and configuration errors

The other reports​

ReportWhat it lists
DomainsEvery domain a listener serves, its TLS certificate and where it goes. Duplicate domains and wildcards that overlap other hosts are flagged.
CertificatesTLS certificates and CA bundles stored in secrets, the soonest to expire first, with the listeners and clusters that use them. Private keys are never read.
Unused and brokenResources nothing references, and references to resources that do not exist. Defaults the platform seeds are marked as such.
ChangesThe audit log of a period (7, 30 or 90 days) summarised by day, resource type and person, with the changes that failed and the most changed resources.