Hi there. I've seen no answers or doc that is related to my question, so, sorry if it exists and I haven't found it yet!
We're an org that uses Sentry for monitoring our various app stages (master, release, preprod, prod...).
Our process for preproduction isn't very clear as anybody can test it and may produce various issues. I would like to introduce "test sessions", which are delimited : for example, a product team member could state that he starts a test session (from a slack webhook for example?) for a specific tag (let's say env: preprod), and state when he ends a test session. goal would be to check in Sentry issues the issues that have been generated during that specific session.
Is there a way to do that, or do you have any advices or resources ?
The ideal would be the following : the product team members specifies when he starts (ideally through slack), every issues are tagged with something related to that session, and could be sent to slack through the integration in a dedicated channel for that session, and the product team member ends it.
To specify, we can't deduce test sessions from users ids or env name.
Thanks in advance 🙂
#Test session tagging from Slack
exotic hill
lucid gorge
I guess I would set a tag with a session ID and then simply filter by that tag + session ID
does that make sense?
exotic hill
it should, but how could I set that tag on every issue that happens between "start session" and "end session", those 2 being two actions I would make on Slack?
lucid gorge
Usually it's as simple as Sentry.setTag('test-session-id', '12345'). In the frontend any error that happens afterwards has that tag
if the session ends you just set it to null
How you hook that up to your slack is up to you
exotic hill
I was looking for a solution that involved communication between Slack and Sentry only, without the apps knowing about those sessions 😄
my apps send traces and issues to Sentry without knowing that those traces/issues could be part of a session.
perhaps, when Sentry receives those, it knows that it has to apply that tag because a session is ongoing (and shouldn't once a "end session" has been received)
this is a solution I'm looking for, of course it could be possible to do so in our apps and I will if this is the only option 🙂
lucid gorge
That is unfortunately not possible.