Verification of SENTRY error notification on self-hosted

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Verify if SENTRY error notification is working on self-hosted platform with specific Docker configuration


Question

Hoping someone could verify if SENTRY error notification works on self-hosted?

I’m running docker in ec2, version 0.50.44

I have defined within my docker environment:

JOB_ERROR_REPORTING_STRATEGY="sentry"
SENTRY_ENVIRONMENT="nonprod"```
Docker up does not return any errors and indicated that Sentry configuration is ok - however no logs ever ship to sentry.

Is there another setting somewhere which needs to be set?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1706925408797939) if you want to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["sentry-error-notification", "self-hosted", "docker", "ec2", "sentry-configuration"]
</sub>
2

Hey Jason, what are you seeing when you say “indicated that Sentry configuration is ok”?

It should indeed work on self-hosted instances. However, note that the only thing that’s sent to sentry is any connector-level errors encountered - not platform-wise. We also only report an error if all sync attempts failed.

3

Thanks <@U038J3BLW3C>

By no error I was referring to docker up being clean without error.

It is possible that I haven’t hit the error yet, although I’m certain I have had pipelines which have exhausted tries and these have not been sent to sentry.

Is there anywhere that I can check to diagnose if it tried to fire to sentry on error?