Observability
Managed Observability on your own cluster
Metrics, logs and traces for your apps: VictoriaMetrics, VictoriaLogs and VictoriaTraces with project-scoped collectors, in one click.
Installed once per cluster and shared by every project on it.
01What it does
Observability, run for you
VictoriaMetrics, VictoriaLogs and VictoriaTraces on their own charts, with a collector per project.
Three stores in one install: metrics, logs and traces, each with the lightweight collector that feeds it, scoped to the project it watches. Install it and the console rewires itself: the Logs and Metrics tabs of every app stop reading raw Kubernetes and start reading the stores, with retention, real queries and history.
Retention is a setting per store, bounded by the disk you give it: when the disk fills the oldest data is dropped before the retention is reached, so size the disk for the window you want. Apps send traces themselves, over OTLP, to the endpoint shown once the service is up.
02Options
What you choose
What the console asks when you create it, in the catalog's own numbers. Anything marked chosen once cannot change without creating a new instance.
- Scope
- Once per cluster
- Metrics
- Kept 7, 15 (default) or 30 days; 10Gi by default, chosen once
- Logs
- Kept 1, 3 (default) or 7 days; 2Gi by default, chosen once
- Traces
- Kept 1, 3 (default) or 7 days; 2Gi by default, chosen once; sent by apps over OTLP
03Adding it
Add Observability to a cluster
Cluster-scoped, so it is added from the cluster rather than from a project, once.
- 01Open the cluster and go to Services.
- 02Pick it from the catalog and choose its options.
- 03Install it. Anyport installs it once for the cluster and tracks its health.
- 04Every project on the cluster can use it from then on; nothing is installed per project.