search

gjcarneiro / yacron

A modern Cron replacement that is Docker-friendly
MIT License
449 stars 38 forks source link

Sentry: fingerprint option doesn't appear to be working #52

Open gjcarneiro opened 2 years ago

gjcarneiro commented 2 years ago

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:

  onFailure:
    report:
      sentry:
        dsn:
          fromEnvVar: SENTRY_DSN
        fingerprint:
          - yacron
          - "{{ name }}"

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.