Back to landing page
Tasks

Observability and Troubleshooting

Use portal status, Grafana, route diagnostics, and workspace state to debug first-app failures.

Use Home for attention items and Observability for telemetry access. Use the domain page that owns the failing object for specific diagnostics: Applications for namespace/GitOps, Data & Services for storage, and Network & Exposure for routes and egress.

First-app checklist

CheckPortal page
Tenant onboarding step is complete or actionableHome
Namespace exists and is reconciledApplications
GitOps source and kustomization are healthyApplications
PVC intent and workload PVC reference matchData & Services
Ingress host and TLS match assigned boundsNetwork & Exposure
Pods, services, and routes have ready endpointsNetwork & Exposure / Observability
Cost and billing state are visibleBilling

Common failures

SymptomLikely causeWhere to look
GitOps does not applyBad repo URL, wrong path, missing credential, or namespace not ready.Applications
HelmRelease RBAC errorMissing Flux service account or chart expects forbidden resources.Applications
Pod cannot read secretOpenBao path or ExternalSecret reference mismatch.Applications
App loses dataPVC intent and workload mount do not match.Data & Services
Public URL shows 404Ingress host is missing or wrong.Network & Exposure
Public URL shows 503Service has no ready backend endpoint.Network & Exposure
DNS seems staleResolver cache differs from route readiness.Network & Exposure
Cost looks unexpectedResource requests, replicas, PVC size, or managed services changed.Billing

RPC/function map

Diagnostic areagh0stplane surface
Tenant attention, checklist, access, and activityGetTenantHomeWorkspace
GitOps, namespace, service-account, and secret workflowGetTenantApplicationsWorkspace, GetTenantSecretWorkflow
Storage, managed service, protection, and restore stateGetTenantDataWorkspace
Network graph, route inventory, observed flows, dropsGetNetworkWorkspace, GetTenantExposureWorkspace
Grafana/access and usage summaryGetTenantObservabilityWorkspace
Billing/payment/invoice stateGetCustomerBillingView

What not to do

  • Do not use direct cluster mutations to fix GitOps-managed workloads.
  • Do not create unbounded NetworkPolicies to "make it work".
  • Do not commit secrets while debugging.
  • Do not move a workload between namespaces without cleaning up stale routes and release-owned resources.

Questions or ready to get started?

Talk to us