Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
gjcarneiro opened this issue Jul 14, 2021 · 0 comments
Open

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

gjcarneiro opened this issue Jul 14, 2021 · 0 comments

Comments

@gjcarneiro
Copy link
Owner

  • Yet Another Cron version: 0.13 (binary)
  • Python version: 3.8
  • Operating System: ubuntu

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant