-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using Sentry with Remix when using Architect (Lambda wrapper) #6062
Labels
hacktoberfest
Meta: Help Wanted
Package: remix
Issues related to the Sentry Remix SDK
Type: Improvement
Comments
AbhiPrasad
added
Meta: Help Wanted
Type: Improvement
hacktoberfest
Package: remix
Issues related to the Sentry Remix SDK
labels
Oct 27, 2022
We need to probably add a wrapper for serverless similar to what we do for express request handling. |
Bump for the fix 🙏 |
Another bump? |
This remains backlogged at the moment due to prioritization of other tasks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
hacktoberfest
Meta: Help Wanted
Package: remix
Issues related to the Sentry Remix SDK
Type: Improvement
Discussed in #6050
Originally posted by alexmk92 October 26, 2022
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 🤯)
The text was updated successfully, but these errors were encountered: