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
Based on production use, running in Kubernetes, a cron jobs that fails creates an Issue in Sentry. When the pod is replaced by a new pod, which changes its hostname, the failing cron job will then create a new Issue in Sentry. Even though I have this in the config:
Based on production use, running in Kubernetes, a cron jobs that fails creates an Issue in Sentry. When the pod is replaced by a new pod, which changes its hostname, the failing cron job will then create a new Issue in Sentry. Even though I have this in the config:
It's as if the fingerprint is being ignored and instead the default sentry_sdk fingerprint is being used instead...
Might have been broken by some sentry_sdk upgrade. Needs debugging.
The text was updated successfully, but these errors were encountered: