At Lumigo. we believe in serverless technology, and our mission is to make serverless development easy and fast. For the past few months, we’ve been extending our observability and debugging capabilities, making it a breeze for developers to understand the end-to-end story of every request that goes through the system, find the root causes of issues and be able to easily address them.
If following the Epsagon acquisition you are looking to switch to the best alternative, Lumigo is the solution for you. Deployment only takes minutes and customizing it to the same setup you had in Epsagon is a breeze.
To help with that, we prepared a simple migration guide below. It walks you through removing Epsagon and deploying Lumigo.
There are several methods for removing Epsagon. Choosing the best one depends on how you installed Epsagon in the first place:
In your Epsagon account, go to Functions, select all functions and click Disable Auto-Tracing from the Actions menu.
Simply delete the instrumentation code that was inserted manually
If you installed Epsagon by changing your functions handlers into Epsagon wrappers and put Epsagon layers to your function configurations:
The handlers of your functions should be reset, and you should remove the Epsagon layer and any environment variables that you have configured.
Use the following command to uninstall:
serverless plugin uninstall –name serverless-plugin-epsagon
This will uninstall the plugin and remove it from the plugins list in serverless.yml.
The Epsagon component can be removed entirely by removing it in the custom section of serverless.yml.
Follow these steps to remove CloudWatch log collection:
Remove the IAM role you created when you set up your Epsagon account.
Creating a free Lumigo account is quick and easy. Sign up for a free Lumigo account and follow the simple instructions in the wizard. You’ll be up and running in a few minutes.
Deploy Lumigo’s tracer is fast, simple, and straightforward, and moreover, you have the option of choosing either auto-tracing, enabling you to take full advantage of its functionality without modifying your source code, or manual tracing.
Learn more about getting up and running with Lumigo.
Lumigo comes with a number of out-of-the-box alerts allowing you to closely monitor your environment and be notified of a problem as soon as it arises. Once you’ve connected Lumigo to your environment, integrate to the services you are using to alert, share, and track issues detected by Lumigo. The services currently available in Lumigo are Slack, Teams, PagerDuty and more.
Learn more about setting up alerts.
With automated distributed tracing, Lumigo visualizes every transaction, allowing you to understand the flow and correlate issues across services.
Easily see the input/output of each service, including 3rd-party services, with environment variables at the time of invocation. View parameters and values in each line of the stack trace. See payload of http and API calls. All this — without any code changes!
For better visibility across your data Lumigo visualizes the frequency distribution of various fields on which you can query, allowing you to quickly detect and compare trends over time and prioritize issues across your applications.
Search with free text in any field that Lumigo collects or use predefined queries as a starting point to answer your questions or create more complex queries by using logical operators to better define the search conditions.
Live Tail, a whole new section in the Lumigo interface, provides a near real-time view of invocations, just like logs, making debugging easy and faster than ever before.
The first step to resolve any problem is to know that you have a problem. The faster problems are resolved and the less impact your users would experience, and for that you need alerts.
Lumigo has you covered with out-of-the-box alerts based on best practices for errors, timeouts, throttling, memory issues, application issues and more, making sure teams quickly get the information they need on their preferred channels as soon as a problem arises.
From issue to the line in code in one-click
Troubleshoot faster by correlating deployment changes and function trends and quickly understand if changes in configuration or a new version of code causes an unexpected outcome such as an increase in the number of invocation failures or degraded performances.
Connect your code repository to Lumigo and find the commit that caused the issue with one-click.