Skip to main content
Clusters are the foundation of Obsy’s infrastructure management. Every OTel collector deployment, sampling config, and telemetry flow is scoped to a cluster. Go to Clusters in the sidebar.

​
Adding a cluster

See Connect a cluster for the full guide. Quick summary:
  1. Clusters → Add cluster
  2. Enter name, display name, and kubeconfig
  3. Click Save — Obsy validates connectivity immediately

​
Cluster detail

Click any cluster to open its detail page, which shows:
SectionContent
OverviewConnection status, Kubernetes version, node count
OTel CollectorCollector health card, install/reinstall button
SamplingActive sampling configuration and quick-edit link
TelemetryLast telemetry received per signal type

​
Connection status

StatusMeaning
ConnectedAPI server reachable, credentials valid
UnreachableAPI server not responding (network issue or cluster is down)
Auth errorCredentials expired or insufficient permissions
Obsy checks connectivity every 5 minutes. If a cluster goes unreachable, a warning appears on the cluster card but existing data (reports, sampling configs) is preserved.

​
Updating cluster credentials

If your kubeconfig rotates (e.g. service account token refresh):
  1. Open the cluster detail.
  2. Click Edit cluster.
  3. Paste the new kubeconfig.
  4. Click Save.

​
Multiple clusters

You can register as many clusters as needed. Sampling configurations, telemetry standards, and reliability reports are managed per-cluster. Incidents, alerts, and services are organization-wide.

​
Removing a cluster

Open the cluster detail and click Remove cluster. This removes the cluster from Obsy but does not uninstall the OTel collector Helm release. Uninstall manually: 
helm uninstall obsy-collector -n obsy-system
kubectl delete namespace obsy-system