OpsKnightDocumentation
⌘K
Start here
Concepts
Guides
Integrations
Operate OpsKnight
Reference
Troubleshooting
  • Troubleshoot database failures
  • Troubleshoot incident processing
  • Troubleshoot installation
  • Troubleshoot integrations
  • Troubleshoot Kubernetes deployments
  • Troubleshoot login and access
  • Troubleshoot notification delivery
  • Troubleshoot status pages
  • Troubleshoot the scheduler
  • Troubleshoot upgrades
  • Troubleshoot workers
    • Worker is unhealthy
Develop OpsKnight
HomeChangelogGitHub
Home/Docs
⌘K
v2.0.0
DocsTroubleshootingWorkers
Troubleshooting1 min read

Troubleshoot workers

Diagnose an unhealthy worker or a queue that is not draining.

Use Worker is unhealthy. Identify the runtime role and lane, then check health, queue age/depth, claim leases, database connections, provider latency, concurrency, and recent logs. Scale only after identifying the actual bottleneck.

PreviousUpgrade migration failsNextWorker is unhealthy

Last updated for v2.0.0

Edit this page on GitHub