Open nunomaduro opened 4 weeks ago
I think that's a good solution.
I don't think we need to remove pulse, it's useful for metrics other than exceptions too.
As your per suggestion: Isolating the pulse data is the key, Then the aggregate data is seperate from user data. We can setup to flatten the data or wipe the db periodically if needed.
Sentry will be excellent upgrade for managing exceptions.
Moving jobs to horizon / Redis might also be worth considering during this process too, or at least put on the roadmap.
Nuno, do we want to:
PULSE_ENABLED = false
in.env
?I feel like keeping Pulse running on production for exceptions, and slow processing is wise before we migrate to something like Sentry.
Whatcha think?