I m curious how other people are handling Sentry + source ma Serverless Stack #help

I’m curious how other people are handling Sentry +...

Sam Hulick

08/19/2021, 12:04 AM

I’m curious how other people are handling Sentry + source maps with Lambda. right now, in my Sentry config, I have

release: process.env.SENTRY_RELEASE

, and each time I deploy,

SENTRY_RELEASE

is the git hash of the current commit. this works fine with associating each function w/ the proper release in Sentry, but the downside is that every time I deploy, EVERY function gets an update. I wonder if there’s a better way to do this

Sam Hulick

08/19/2021, 12:04 AM

@thdxr this is probably up your alley

thdxr

08/19/2021, 12:05 AM

I only load one env variable in every function which is SSM_PATH =

/${dev.stage}/

and then all my variables are loaded from SSM on lambda cold start

Sam Hulick

08/19/2021, 12:06 AM

got it. so for the Sentry release hash, how do you update that in an automated fashion when you deploy?

Sam Hulick

08/19/2021, 12:07 AM

(perhaps just an SSM update via AWS CLI?)

thdxr

08/19/2021, 12:23 AM

I would update that via CDK

Sam Hulick

08/19/2021, 12:24 AM

ahhh.. right!

Sam Hulick

08/19/2021, 2:42 AM

@thdxr that works great! only about 50ms cost to pull an SSM parameter, then it’s cached while the func is warm. so, obviously the Sentry initialization has to be wrapped in a function now since it has to make an async call to SSM. how do you have that set up so every single Lambda function does that? trying to think if there’s a better way than importing a function all the time & doing

initSentry()

Sam Hulick

08/19/2021, 2:44 AM

I suppose some sort of higher-order function wrapper around the Lambda handler would work. though it still requires an extra step

Open in Slack

Previous Next