You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When going through some Sentry issues I found myself wanting a bit more from the tags:
We should send the docker image as a separate tag, since the release tag is hiding the "package name" and only showing the version, making it a little more work to know what connector this is affecting.
workspace_id should also be a separate tag - currently it comes through as the user, which is workable but not quite clear
When working with the issue I often wanted to go into the affected workspace/connection. I can build that link myself by using the workspace id and connection id that are already included in the tags, but we can probably include a direct link instead.
Other notes:
deployment_mode is currently coming though as OSS. I would expect this to be cloud instead - are we not setting the env variable?
The text was updated successfully, but these errors were encountered:
When going through some Sentry issues I found myself wanting a bit more from the tags:
workspace_id
should also be a separate tag - currently it comes through as the user, which is workable but not quite clearOther notes:
deployment_mode
is currently coming though asOSS
. I would expect this to becloud
instead - are we not setting the env variable?The text was updated successfully, but these errors were encountered: