Diting Labs
Talk to us

One map for mixed estates

Clusters, workloads, network, storage, events and hosts in one view.

Half in the cluster, half on a VM

Few estates moved to the cloud in one step. New services run in Kubernetes, older ones on virtual machines and bare metal, with databases and queues in between.

Clusters and hosts share one topology, permission model and alert path.

Onboarding order

  1. Connect clusters

    kubeconfig or in-cluster agent, authorized per cluster.

  2. Connect hosts

    Install the agent on VMs and bare metal.

  3. Link relationships

    Services, pods, hosts and databases connect automatically.

  4. Set access

    Grant by cluster, namespace and host group.

Hybrid topologyDiting
Cluster
Namespace
Workload
PodPodPod
Kubernetes and virtual machines in one call graph.

Events, logs and metrics

Workload state, events, logs, metrics and traces all on this page.

  • Clusters and nodes
  • Workloads and events
  • Network and storage
  • Hosts and kernel

Fits

  • Multi-cluster, hybrid cloud, Kubernetes plus VMs
  • Teams that need release and cluster state together

Doesn't fit

  • Fully managed black-box clusters with no API and no agent allowed

Bring your system in

Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.

Talk about your estateRead the docs