Skip to content

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

@gjcarneiro

Description

@gjcarneiro
  • 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions