Riccardo Busetti

Updated production configs with the fixed DSN and discovered a bug in the SDK which the team is fixing with this PR: https://github.com/getsentry/sentry-python/pull/3047/files

SNS is working on the implementation of this function, which we will have to call from the metrics API code: https://www.notion.so/sentry/Metrics-layer-resolve-time-interval-mismatches-b6830ecd06534e52b66e7db64e8ed9b9#37441fb9e85842e6a3c9a2bacb6092c8

For now, we will do this only in `metrics/data` but I will follow up with an analogous PR on the `metrics/query` endpoint.

Hi, sorry, I completely missed the notification. I will check it out!

This test replicates the error: ```python def test_attachments_with_form_data( mini_sentry, relay_with_processing, attachments_consumer, outcomes_consumer ): project_id = 42 event_id = "515539018c9b4260a6f999572f1661ee" mini_sentry.add_full_project_config(project_id) relay = relay_with_processing() attachments_consumer = attachments_consumer() outcomes_consumer = outcomes_consumer() #...

The problem was found, we are discussing offline what is the expected handling of form data. If it should be converted into its own event or produced as attachment.

Closing this issue since we have one more descriptive here: https://github.com/getsentry/team-ingest/issues/275.

Hi, did you experience any overload of Redis when the errors started happening?

Hi, thanks for the report. We did some analysis of `sysinfo` and discussed internally. We are unsure about the best approach moving forward since we rely on `RSS` when using...

We added this request to our internal board! We will track the work and follow up in case of any doubts/updates, thanks for reporting.