Replies: 1 comment 1 reply
-
Yup you are on the money. Going to transfer this into an issue so we can track as a feature request (improving remix integrations here). PRs are welcome if you have any ideas. In terms of the Lambda extension - not sure, will ask around about it. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We've built a new product at work which is using Remix and deployed to the edge using Architect (wrapper around CloudFormation and Lambda)
It's working great, but we're massively missing out on visibility into the app. I installed the Remix SDK today and it works great for reporting client side metrics; the server-side however receives no information due to the fact we're not using Remix's default server execution handler.
In the interim, I've pulled in the
serverless
SDK as well as the Remix SDK and exported the remix Lambda handler after initialising the app using the Remix SDK:I'm now getting some metrics out of my server-side code, but its very limited in use as all routes are named as
AppEnvAnyCatchAllHttpLambda
. I'm guessing this is where a dedicated remix wrapper would need to be created to add additional meta information to the trace (such as the route, params etc)What steps would I need to take to provision a Remix Lambda extension? I'm happy to tinker with it, I've just got no idea where to start (the existing Lambda implementation was a bit over my head 🤯)
Beta Was this translation helpful? Give feedback.
All reactions