Lightrun Pros and Cons

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.

It's powerful. Lightrun can be used to debug and profile frontend applications in real time, without the need to deploy your code to a staging or production environment. This can save you a lot of time and frustration when trying to track down bugs.

It's easy to use. Once you get the hang of it, Lightrun is very easy to use. You can add breakpoints, inspect variables, and even step through your code, all without leaving your browser.

It's constantly being improved. The Lightrun team is constantly adding new features and fixing bugs. This means that Lightrun is only going to get better over time.

Overall, I think Lightrun is a great tool for debugging and profiling frontend applications. It's powerful, easy to use, and constantly being improved. However, it's important to be aware of its limitations, such as the fact that it can be difficult to get started and that it can add some overhead to your application. If you're looking for a simple and easy-to-use debugging tool, Lightrun might not be the best option for you. However, if you're willing to put in the time to learn how to use it, Lightrun can be a powerful tool for improving the quality of your frontend code. Review collected by and hosted on G2.com.

Nothing to dislike about Lightrun. Lightrun is a powerful and innovative tool for debugging and profiling frontend applications. The company is constantly improving the product and documentation, which can sometimes create operational challenges for us. However, Lightrun support is always quick to help and resolve any issues. Review collected by and hosted on G2.com.

They offer free trial, so I could easily set it up on my project and see if it actually fits. Many of the other solutions require to pay upfront. Review collected by and hosted on G2.com.

I think that the UI could be better. I guess it's a matter of taste but it would be nice if I could customize a personal theme. Review collected by and hosted on G2.com.

I like that it helps me know which code flows are really used, espically the sanpshot feature which allows me to look at the call stack.

The tool helps me validate my hypotisis when something goes wrong.

We also have a Slack channel with Lightrun support which are super responsive and helpful.

It's a valubale tool, easy to use, that I use very frequently. Review collected by and hosted on G2.com.

Conditional breakpoints doesn't always work due to the fact that it might hurt production performence. Review collected by and hosted on G2.com.

As a consultant, I've seen the ins and outs of countless developer tools across various companies. Best practices and good tools exist, but they generally need to be planned in advance and often require a sizable dedicated team to manage (and sometimes use...)

Lightrun has made my job of helping teams easier.

In my case, I've implemented Ligthrun to debug Kubernetes applications.

For developers, the whole Kubernetes debugging process becomes more accessible, even when Kubernetes skills are not across-the-board in the team. Instead of messing around with complex setups, they can dive right into the app, throwing in logs, metrics, and traces on-the-fly. It's basically a debugger that works on remote live applications, including in production, and it works well in a container environment.

And let's not forget the operation teams. The on-demand logging is especially useful especially when considering the budget (both licensing and storage) to host logging applications. Review collected by and hosted on G2.com.

As far as the programming language you're using is supported, nothing to dislike. Go support would be helpful. Review collected by and hosted on G2.com.

Lightrun stands out for its rapid troubleshooting capabilities, allowing us to resolve complex database issues quickly, bypassing the need for extensive data replication. Its seamless integration with VS Code and user-friendly debugging features enhance its utility in development environments. The responsive customer support through Slack is a significant advantage, offering immediate assistance without the usual delays of traditional ticketing systems. Review collected by and hosted on G2.com.

While the VS Code extension could benefit from minor UI improvements, the overall experience is greatly enhanced by the supportive and receptive Lightrun team, who are committed to continuous improvement based on user feedback. Review collected by and hosted on G2.com.

Lightrun is a fantastic and dynamic tool to have live debuging session without having any impact on live environment.

It has great capabilities to add logs, snapshots and debugger session to any live running environment without any code change or redeployment required.

Also it is light weight so add negligible overhead on the application infrastructure.

Loved the tool. Review collected by and hosted on G2.com.

Not exactly a dislike but would like tool to have capabilities to have better retention of the captured logs and snapshots. Review collected by and hosted on G2.com.

Log and snashot are best i have ever use to debug any issue from light run. Review collected by and hosted on G2.com.

It has limited to line level specific veriable scope to snapshot object details, It would be nice if it is at class or method level Review collected by and hosted on G2.com.

Adding Lightrun actions is straightforward just like a local breakpoint is working, but remotely.

It is very simple to add a snapshot and a log directly within my code

I am using Scala and for me, debugging without the need to recompile and redeploy my code, is a great time saver. Review collected by and hosted on G2.com.

Using the “evaluate” field sometimes not working for me. I assume I’m not using it correctly. I sometimes get the following error: “Invalid expression syntax” Review collected by and hosted on G2.com.