While AWS Lambda is the leading serverless computing platform, it has a lot of functionality (tags and functions) to deal with all kinds of web related actions, stuff still breaks when in production. With NerdVision, you finally have access to an enterprise-class non-breaking collaborative debugger, enabling you to easily set breakpoints and add watches without halting program execution - in production, built and backed by the makers of FusionReactor.
Speed and simplicity make this the perfect solution to quickly test a hypothesis of what could be wrong with an application so you can dramatically reduce issue isolation time.
Better yet, you can debug in production safely knowing that NerdVision never sees any of your code as the code is never on our servers.
It's crazy, you're using new lightweight dynamic scripting language and still debugging production errors like it's 2001. Yeah, this issue has been debated for a long time with the 2 most common approaches being to;
1. Configure a remote debugger through an IDE, or
2. Add logging to your application to gain insight into your issues.
However, there are several disadvantages for both of these techniques, let alone getting sufficient logging for production environments that can be a challenge. Additionally, remote debugging has historically been seen as unsafe for production - until now.
Isn't it time your debugging matched the rapid deployment you enjoy with Lambda and made your life a little easier? Thankfully, NerdVision provides the solution to safely debug in production, without the need for a remote debugger or excess logging.
While we're focused on debugging in production because of the inherent challenges, it's a tool you can put in your toolbox and use in every stage of the application lifecycle, from development to production, and will work in exactly the same way no matter where your application is hosted.
The days of restarting or redeploying your applications to debug are gone.
Capture the full stack trace and all of the variables needed. To debug efficiently you need to have enough data, using your NerdVision app, you have access to all variables and the stack trace to see exactly what caused your breakpoint to fire.
Fire breakpoints only on specific instances. An issue may only be occurring in a specific configured environment, you can now filter which instance or group of instances to debug.
Conditional breakpoints. Reproducing an issue in production is never simple. Guess what? You can easily set conditions that must be met for a breakpoint to fire based on the variable or environment state. Learn how to set a conditional breakpoint.
Having an enterprise-class production-ready debugger for when you need to debug in production will provide you with the ability to have insight into any environment and resolve issues more efficiently.
Monitoring your IDE and waiting for breakpoints to fire is not an efficient use of time. Instead, your NerdVision application will notify you via email or Slack when a breakpoint has fired.
Create workspaces directly from GitLab, GitHub repositories on the master and branches to debug in production and staging environments.
Code is always evolving, whenever your code is updated this will be reflected within your NerdVison application.
Having many small applications rather than one large application is becoming the recommended
way to develop applications.
You can quickly switch between multiple workspaces to debug an issue and find the root cause of an issue in distributed environments.
Sign into your NerdVison application using authentication from your existing Google, GitHub, or GitLab accounts.
ColdBox Platform Supported in NerdVision App
Install NerdVision with 3 quick commands commands.
With no overhead, you can installed 24x7 and debug whenever you need
Configuring logging or debug arguments when you have an issue is a thing of the past.
Try it free for 14 days.
