K8s Troubleshooting, Built for Developers

Identify application-level issus in any Kubernetes cluster – including EKS, GKE, AKS, OpenShift, Minikube and others – with debugger-grade information and without ever leaving the IDE.

  • Add logs to live pods without stopping the running application or losing state
  • Troubleshoot across pods, namespaces and even entire clusters
  • Debug in Kubernetes without port-forwarding and other ops magic

Kubernetes Observability, No Ops Required

Lightrun enables developers to add logs, metrics and traces to live applications without needing to restart, redeploy or even stop the live application.

All Lightrun actions can be added without requiring any additional configuration, which means there’s no need to:

  • Change neamespaces
  • SSH into a pod
  • Port-forward a local port to a pod’s port
  • Read or write any YAML

Easily Follow the Path

Lightrun chooses the active apporach, rather than the passive approach, to telemetry.

Instead of adding as many logs as possible to each of your services then figure out which pod emitted which log in profduction, only add the logs you need at runtime to the relevant pod(s).

This way, it’s easy to trace the exact path the application took in each step of execution.

Remote Clusters, Local Experience

Lightrun works completely within the IDE, allowing you to “pop the hood” of your application right next to its source code.

Every single Lightrun Action is added from the IDE and instrumented in real-time in your cluster, with its output automatically delievered to your IDE.

No scrolling through web-based GUIs, no terminals and no extra configuration required – it’s like using a debugger that just works, everywhere.

Get Down to Business

Let one of our Observability Specliasts walk you through

Lets Talk!

Looking for more information about Lightrun and debugging?
We’d love to hear from you!
Drop us a line and we’ll get back to you shortly.

By submitting this form, I agree to Lightrun’s Privacy Policy and Terms of Use.