You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Epsagon is no longer operating. They took down their website on 3
October and backend services have been gradually removed, and since 10
October any service still making requests to Espagon servers faces
delays and Lambda timeouts.
We have now migrated to [Lumigo]. Their platform supports
[auto-tracing], allowing us to begin monitoring without deploying
updates to Lambda Wrapper, however we are missing our metrics and labels
which correspond to [Execution Tags] in Lumigo.
This PR makes the change to wrap handlers with Lumigo's tracer, and
updates our logger to use Execution Tags for metrics and labels. To
enable Lumigo tracing and tags, set `LUMIGO_TRACER_TOKEN` in your Lambda
environment to your [Lumigo token]. Note that if you have enabled
auto-tracing, this will be set automatically and tracing should "just
work".
There are a couple of other little things that need doing (e.g. removing
the `raiseOnEpsagon` flag) that I'll cover in separate PRs.
Jira: [ENG-2764]
[Lumigo]: https://lumigo.io/
[auto-tracing]: https://docs.lumigo.io/docs/serverless-applications#automatic-instrumentation
[Execution Tags]: https://docs.lumigo.io/docs/execution-tags
[Lumigo token]: https://docs.lumigo.io/docs/lumigo-tokens
BREAKING CHANGE: We no longer use Epsagon for monitoring. Lambda Wrapper
now supports [Lumigo](https://lumigo.io/) instead.
At Comic Relief we use [Lumigo](https://lumigo.io/) for monitoring and observability of our deployed services. Lambda Wrapper includes the Lumigo tracer to allow us to tag traces with custom labels and metrics ([execution tags](https://docs.lumigo.io/docs/execution-tags)).
210
+
211
+
Lumigo integration works out-of-the-box with Lumigo's [auto-trace feature](https://docs.lumigo.io/docs/serverless-applications#automatic-instrumentation). If you prefer manual tracing, enable it by setting `LUMIGO_TRACER_TOKEN` in your Lambda environment variables.
212
+
213
+
And if you don't use Lumigo, don't worry, their tracer will not be instantiated in your functions and no calls will be made to their servers unless `LUMIGO_TRACER_TOKEN` is set.
214
+
207
215
## Notes
208
216
209
217
Lambda Wrapper's dependency injection relies on class names being preserved. If your build process includes minifying or uglifying your code, you'll need to disable these transformations.
0 commit comments