Welcome to Lightrun Blog

So many things can fail when dealing with persistence. We can usually inspect the end result but understanding…

Java is a wonderful, powerful and versatile language/platform. It’s very easy to debug under normal conditions but when…

Spring applications need a fair amount of configuration. Things like Maven dependencies, MVC configuration, and security all require a lot of code to get up and running. Spring reduces or eliminates these needs entirely, instead allowing you to override any of the defaults it selects for you.

Sometimes, remote debugging is necessary. In the simplest terms, remote debugging is debugging an application running in a remote environment like production and staging.

What if we could also prevent security issues in our code before we ship it? What if we could code-level visibility into what's going on inside our production applications, right there in the IDE?

DevOps teams can’t hope to run a tight ship without managing their services. Communication and visibility are absolutely crucial in a Kubernetes system. Accordingly, service discovery describes the process of connecting to a given service within your ecosystem.

Developers can use a combination of a robust observability stack to collect, transform and view logs application-wide, paired with a real-time observability platform that can augment the log stream without pushing new code, re-deploying, or even restarting the service. That’s how Elastic and Lightrun can tame that beast together. 

In this article, you’ll learn how to configure Visual Studio Code for remote debugging by using the powerful remote development extensions it offers.

We’re pleased to announce the release of Lightrun’s developer-native observability platform for Python!

  TEL AVIV - August 5, 2021 - Lightrun, the leader in IDE-native observability, today announced support for…

As software got more complex, more and more software projects rely on API integrations to run. Some of…

As a developer, you’re going to be making changes to a codebase. That’s why, as Harold Abelson put it, “Programs must be written for people to read.” If a codebase is not clearly formatted, debugging becomes more difficult than it should be.