Let us know if you have any more questions by chatting with us using the help widget.
Epsagon uses tracing to extract events from the production code. After setting Epsagon in your services, either automatically or manually, it will instrument the code every time it's loaded. While the code is running, events will be sent to Epsagon and analyzed in real-time to generate tracing maps, alerts, and insights.
Epsagon was built for modern cloud applications. It means that you can use any kind of workload since Epsagon does not use executable agents. It's operating only at the code-level, using a lightweight agent SDK, which allows it to run on containerized applications, serverless, or any other scenario.
No. Epsagon supports a variety of common frameworks in multiple languages and will do all the instrumentation automatically for you. If you're using AWS Lambda, you can use our auto-tracing technology to have the Epsagon layer automatically included in your Lambda functions, which no code changes required whatsoever.
Inviting team members are free at Epsagon. Head to your settings page and just invite them by typing their email, or list of emails separated by a comma.
To change the owner of your account, please contact us at How to Get Help.
To set up SSO login for your account, please contact us at How to Get Help.
To set up an email for billing, please contact us at How to Get Help.
You can fully control the data that is being sent to Epsagon. Read more at the Security and Privacy section.
To completely remove the data from an application, head to the archive tab of the settings page, and archive the desired applications.
To deactivate or close your account, please contact us at How to Get Help.
Integrating to the environment requires certain permissions, that some of them can be modified upon request. For the tracing, no permissions are needed, except for whitelisting outbound traffic to the Epsagon collectors.
To find your Epsagon token, go to your settings page, and you'll see your token:
Make sure your code is accessible to the internet. If you need to whitelist specific IPs you can use the following list based on your region (port: 443):
|US East (Ohio)|
|US East (N. Virginia)|
|US West (N. California)|
|US West (Oregon)|
|Asia Pacific (Mumbai)|
|Asia Pacific (Seoul)|
|Asia Pacific (Singapore)|
|Asia Pacific (Sydney)|
|Asia Pacific (Tokyo)|
|South America (São Paulo)|
In addition, make sure that your account didn't run out of quota. To check that, head to your billing page.
If you still don't see any trace, contact us at the How to Get Help.
You can add
DISABLE_EPSAGON=TRUE as an environment variable to completely disable in local, tests, or dev environment.
Epsagon does not recommend sampling traces, especially in distributed environments. If you still wish to consult with us, contact us at the How to Get Help.
If you choose, you can use our layer in your Python or Node.js function instead of installing it.
- Python layer ARN:
- Node.js layer ARN:
To get the latest layer details you can get to this endpoint:
When using the Epsagon auto-tracing on Node or Python functions, it adds a layer and updates the handler to point to a file in it. Since it can't be opened, the following notice appears:
This is NOT an issue, the function is completely fine - Your function is still running regularly, and you can edit the files.
In Node you'll see the message -
Lambda can't find the file /opt/nodejs/node_modules/epsagon.js. Make sure that your handler upholds the format: file-name.method.
In Python you'll see the message -
Lambda can't find the file epsagon.wrapper. Make sure that your handler upholds the format: file-name.method.
Yes. You can follow this tutorial.
Invocations, log view, and alerts are currently not available for this function / Function subscribed to a different consumer
In order to parse invocations, Epsagon subscribes to your CloudWatch log group and parse it. Since there is only one destination that can be applied, if you found the following warning next to your function:
It means that your function is already subscribed. To fix that, we can subscribe the logs to Epsagon, or provide you with a solution to stream logs to multiple destinations. Contact us at the How to Get Help.
Getting ROLLBACK_COMPLATE when deploying the CloudFormation stack / Can't deploy the CloudFormation stack
If you are facing any errors deploying the Epsagon CloudFormation stack, first make sure that it is not already deployed in your account. To do that you can look for a stack named Epsagon in your CloudFormation dashboard, or an IAM role named EpsagonRole.
In such cases or any other issue contact us at the How to Get Help.
Updated 17 days ago