Skip to main content

Diagnose

The diagnose tool gives you a fast way to understand why a scope is not working as expected.

Instead of guessing whether the problem is related to networking, pods, services, or configuration, Diagnose runs automated checks on your agent-backed scope and presents clear results, logs, and guidance so you know where to start.

Agent support

Diagnose is on by default for new agents. If yours is older, upgrade the agent to enable the feature.

Diagnose your scope​

Diagnose is an action you can run from the UI on agent-backed scopes.

When you run Diagnose, the agent:

  • Collects a snapshot of your scope’s Kubernetes resources
  • Runs a set of predefined checks
  • Groups results by area such as Networking, Scope, and Service
  • Shows which checks passed, which failed, and why

Each check focuses on a specific condition. For example, Diagnose can tell you whether an ingress exists, whether pods are running and ready, or whether services have healthy endpoints.

What happens when you run a diagnosis​

A Diagnose run follows a simple flow.

First, Diagnose captures a snapshot of the Kubernetes resources related to the scope. This ensures all checks evaluate the same point in time.

Then, the checks analyze that data and report their results independently. This keeps the experience fast and consistent, even as more checks are added over time.

💡 Note: You do not need to configure anything. The full flow runs automatically when you click Diagnose or when a scope fails.

What Diagnose checks for you​

Diagnose runs default checks grouped into three categories.

Networking​

Networking checks focus on ingress, routing, TLS, and load balancer configuration. They help you identify issues related to:

  • Ingress existence and class validation
  • Backend service connectivity
  • TLS certificate configuration
  • ALB capacity and synchronization checks

Scope​

Scope checks focus on the workload itself. They surface problems like:

  • Image pull failures
  • Container crashes and restarts
  • Missing resource limits
  • Pod readiness issues and volume mounting errors

Service​

Service checks validate service configuration and connectivity. They help ensure:

  • Service existence
  • Selectors match running pods
  • Endpoints are available
  • Ports are configured correctly

Each check shows a clear status, explains what it found, and gives you access to logs for deeper investigation.