Packit-service: make it configurable to send events to sentry

[TomasTomecek]

This is a follow-up to https://github.com/packit-service/packit-service/pull/544

We should have a new packit-service.yaml config option to configure if we want to send events to sentry.

[IceWreck]

I'll try tonight.

Regarding the setup, if I set-up a sentry account, provide sentry credentials in an env var and deploy, then will it automatically start sending events/tracebacks to sentry? Or is there any other config involved too?

I only have to provide SENTRY_SECRET=https://<key>@<organization>.ingest.sentry.io/<project> right?

[TomasTomecek]

You're correct! In p-s we have this set up via openshift secrets, defined here and the content of the secret looks like this: https://<ugly-string>@sentry.io/<our-id>

[IceWreck]

While working on this, I noticed that while the code to run sentry for the service container is present, its effectively disabled by not providing SENTRY_SECRET to this container

Secrets are only passed for packit-worker and the fedora-messaging container.

If i do provide them to the service container, it errors out with
RuntimeError: Signalling support is unavailable because the blinker library is not installed.
Sentry docs do not mention needing blinker if sentry-sdk[flask] is installed, which is installed, in our case.

Although this is not directly related to this issue, I felt it was worth mentioning / asking about.

[TomasTomecek]

@IceWreck good point, would be nice to set up sentry for service pod as well

[IceWreck]

👍. I'll start working on setting up sentry for service later this week then.