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
We aren't currently writing this event to eventstore in the issue platform. We have a couple of options here:
As part of our ingest pipeline, write the event data to eventstore and keep using it as before.
In post_process_group, when dealing with an issue platform issue, instead of using eventstore we could fetch the event from nodestore. This might make things better for our overall architecture in the future, since we won't have to wait for the slow post_process_group step to complete before we clear the cache.
As well as this, we need to make sure to fetch the occurrence and associate it with the GroupEvent. To do this, we'll need to pass the occurrence id along to post_process_group and load it from nodestore.
The text was updated successfully, but these errors were encountered:
Currently,
post_process_group
is passed a cache key, which is used to fetch the event from eventstore:sentry/src/sentry/tasks/post_process.py
Lines 332 to 343 in 5d00683
We aren't currently writing this event to eventstore in the issue platform. We have a couple of options here:
post_process_group
, when dealing with an issue platform issue, instead of usingeventstore
we could fetch the event from nodestore. This might make things better for our overall architecture in the future, since we won't have to wait for the slowpost_process_group
step to complete before we clear the cache.As well as this, we need to make sure to fetch the
occurrence
and associate it with theGroupEvent
. To do this, we'll need to pass the occurrence id along topost_process_group
and load it from nodestore.The text was updated successfully, but these errors were encountered: