my goal is to improve error reporting by giving ability for devops to connect issues seen in Sentry to the issues on the backend. I have two questions:
Is `attach_stacktrace option documented here https://docs.sentry.io/platforms/rust/configuration/options/ automatically attaches X-Trace-ID HTTP header to the log? Presumably this option is turned on by default but when I inspect issue log in Sentry I can’t see trace id logged anywhere
What is the best way to listen to Sentry’s attempts to send error events? We have several browser plugins for internal usage that automate operational things and I’d like to get some info about the issue that Sentry is logging (issue id, trace id etc).
Any information is appreciated