sentry | Production ready Sentry configuration for Docker Compose | Monitoring library

With sentry_sdk, the sentry documentation explain how to automatically catch exceptions or logging messages. However, how can I catch a python warning, like a DeprecationWarning that would be raised with

How to send specific information in Sentry ? There is Events in documentation but how to use them properly and where exactly to use them (EX: Send user email with the error) ?

Sentry provided this source code but where exactly I have to use it? :

I am working on project upgrade from Vue 2 to Vue 3. The code base changed according to Vue migration documents: https://v3.vuejs.org/guide/migration/introduction.html#overview. I have mismatch of above mentioned libraries. Does somebody has a running project and would share their working library versions

Current mismatch error is :

I am using Wistia API for video upload. The code seems to be fine and according to Wistia docs but when I upload a file, it shows the progress going from 0 to 100%, but after reaching 100%, following error is logged in console by sentry:

I've recently added Bull to my project to offload things like synchronizing documents to 3rd party services and everything's working well, except errors occurring while processing jobs don't end up in Sentry. They're only logged on the jobs themselves, but since we're running our application on multiple configurations, it means I have to constantly monitor all these instances for job processing errors.

I know I can add an error handler to a processor, but I have quite a few processors already, so I'd prefer another, more global, solution

Is there any way to make sure these errors are also sent to Sentry?

I tried to follow every comment with a possible solution here to the letter. I relied on an example project on github as well which works perfectly.

This also started to happen to me after updating everything manually and when running the nx test command, occurrs this error.

My jest.config.js inside apps/my-app:

There are many situations where I know an error will occur and want to pass additional data to Sentry. I still want the exception to get raised (so the rest of my code stops) and I only want one error in sentry.

For example, let's say I'm making an HTTP call and, in the event that the HTTP call fails, I want an error including the response text sent to Sentry:

I have been trying to send a ".log" file attachment to sentry from python every time an error/ exception occurs but so far without success. Sentry does not provide attachments documentation for python, so I have been reading the java attachments example (https://docs.sentry.io/platforms/java/enriching-events/attachments/), which is

My goal is: I want to step into the some line of code of STL istream. So I used custom built "LIBC++13" with "Debug" build type(the command I used are shown at the bottom), so that (I think) I can get a fully debuggable version of STL, and be able to step into everything I want. But I got a problem.

Here are my breakpoints settings for istream, BREAKPOINT A(Line 1447) and want to step into Line 310: