Lightrun Pros and Cons

Its ability to seamlessly integrate with IntelliJ, allowing for real-time debugging without disrupting the workflow. The snapshot feature is particularly powerful, enabling me to pinpoint issues in complex, multi-service environments with ease and efficiency. This significantly accelerates the debugging process and enhances overall productivity. Review collected by and hosted on G2.com.

the only option is to log the data, I would like somehow to debug it step by step. Review collected by and hosted on G2.com.

Lightrun's best feature is that it is easy to integrate with any environment, be it production or lower environments. This amazing tool allows you to add a virtual brealpoint in application code and whenever that code gets a hit, it will capture all the data in a snapshot at that particular point. Also you can add conditions and expressions for when you want to capture the snapshot, making it easy to bifurcate from all the generic requests. The easy to use tool is acting as a game changer to debug and test your code. Review collected by and hosted on G2.com.

The tool is on the right path of its growth, Lightrun is constantly evolving itself with user needs and our feedback is actively taken for constant improvements. I am sure the tool has a great future plus working with this folks is super amazing as their primary goal is user satisfaction! Review collected by and hosted on G2.com.

The agent approach is the way to go, used by many other specialized tooling solutions. The logging feature is very nice and it suports standard Java conditions evaluation. Snapshots are the most useful because you can add them anywhere you need. Also, you can use either IntelliJ IDEA or Visual Studio Code to use Lightrun plugins, which are easy to use. Finally, you can have as many agents as you need along with your deployments, which can be configured to run with minimal resources in order to not detriment environment resources. Review collected by and hosted on G2.com.

You need to have the deployed source code version you want to debug using Lightrun and most features are only supported for Java and Node.js right now. Also AI features are not yet ready, but do look very promising! Review collected by and hosted on G2.com.

Being able to easily see within running prod environment apps is very helpful for debugging issues and can show information that you could never get without running the app locally, which can become very difficult in setups with many apps communicating between themselves. The actual writing of logs is easy and setup isn't too difficult Review collected by and hosted on G2.com.

When Lightrun logs throw errors it can be difficult to parse why they're happening. Sometimes there will be errors for "unreachable code" when I know the code is getting hit and it can be hard to figure out why a log is failing Review collected by and hosted on G2.com.

Great customer support and relations,

The people in lightrun helped us with implementation and use cases, and followed up with us along the way.

Great tools and options for on the fly debugging and problem investigation. Review collected by and hosted on G2.com.

Plug ins to the IDE can be a little difficult to use from time to time Review collected by and hosted on G2.com.

Lightrun has become an essential debugging tool for our team. Its ability to capture snapshots during runtime, plus its speed, efficiency, and user-friendly features significantly improve our development workflow and ultimately, our ability to deliver a positive customer experience. Review collected by and hosted on G2.com.

accasional delays and small bugs that interrups workflows Review collected by and hosted on G2.com.

Lightrun makes it very easy to observe and debug our apps in runtime, because of that we have become more shift left ready. By allowing to inject telemetry directly from the developer machine we are able to reduce our MMTR in critical issues which significantly helped derisk and bring tangible cost reduction. Combining this with continuous testing via automation, mock services and API monitoring, we have a pretty solid pipeline in place now. Review collected by and hosted on G2.com.

I wouldn't say dislike but I think more examples like the online playground would make ease our team adoption and usage further. There is a small learning curve, but like everything useful it's kind of part of the fun too. Review collected by and hosted on G2.com.

The ability to dynamically inspect variable values and performance in real-time while troubleshooting an application in production. While we all work very hard to create our unit and functional tests, some situations have not been anticipated. In these circumstances, nothing beats being able to do what LightRun can do. Review collected by and hosted on G2.com.

The one challenge I have run into is how I deployed the agent. On traditional VMs, it would have been wiser to deploy the Instana code with the application instead of in a central location - or to have a configurable way to select the deployment location and have multiple locations on the VMs. Review collected by and hosted on G2.com.

Lightrun allows you to debug code remotely in Intellij super fast without any nasty ports being opened in Production and connect to a specific pod/node if required to isolate the problem real quick and remediate it.

Adding loggers is a plus too to observe values real time Review collected by and hosted on G2.com.

The UI for Intellij plugin can be worked upon more for searching tags etc and integration for NewRelic and splunk can be more verbose in docs for Infra teams to understand.

Also if they can have some mechanism of integrating agent keys in a different way and not have to add arguments to each agent which can be a lot of services in an org that would make adoption smoother and faster Review collected by and hosted on G2.com.

One of the best thing I loved about Lightrun is that the setup time is very minimal and then developers have full flexibility to take snapshots of heap or logs at any line of the code.

This helps us move into a new direction of development wherein devs dont bother about putting a log statement just for debugging, which would often need a redeploy if log statements were missing. Review collected by and hosted on G2.com.

Nothing to dislike as such. If I have to think about a point then I feel the UI of IntelliJ plugin can be more intuitive. There is only a slight learning curve Review collected by and hosted on G2.com.