Web Adapter startup process breaks other lambda layers that modify startup #412
Unanswered
rposbo-selfridges
asked this question in
Q&A
Replies: 1 comment
-
In this setup, you could treat the nextjs application as a standalone application running in a docker container. Could you try their instructions for App Runner and let me know the results? I don't have access to Dynatrace. Otherwise, I would have tested it myself. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
We're using the Dynatrace OneAgent lambda layer to integrate nextjs applications, as containers, hosted in aws lambdas with our observability platform.
Unfortunately, this has proven impossible as the web adapter seems to trigger the lambda directly instead of modifying the runtime startup (?) - this is a bit beyond me, so the feedback from Dynatrace tech team is below:
Is this something that can be altered such that both the web adapter and the dynatrace one agent lambda layer can work side by side?
Expected Functionality
An AWS lambda hosting a nextjs application, as a container, using both the aws lambda adapter and the Dynatrace OneAgent lambda layer, results in 1) a nextjs application that can both serve web requests, and 2) lambda telemetry reported to Dynatrace without instrumentation within the application code itself
Actual Functionality
An AWS lambda hosting a nextjs application, as a container, using both the aws lambda adapter and the Dynatrace OneAgent lambda layer, results in only a nextjs application that can serve web requests
Beta Was this translation helpful? Give feedback.
All reactions