Trouble configuring Sentry integration for Airbyte connectors

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

Summary

User is facing issues configuring Sentry integration for Airbyte connectors in a Kubernetes deployment. Environment variables are set but errors are not reported in Sentry. Suspecting an issue with the allowedHosts value in the self-hosted Sentry instance.


Question

Hello! I’ve been trying to configure Sentry integration for Airbyte connectors, but having trouble doing so and can no longer find the relevant https://docs.airbyte.com/operator-guides/sentry-integration/|docs. I stumbled upon this <Slack post> from 9 months ago. I’ve set the following variables:

  env_vars:
    JOB_ERROR_REPORTING_STRATEGY: "sentry"
    JOB_ERROR_REPORTING_SENTRY_DSN: "<sentry_dsn>"
    SENTRY_DSN: "<sentry_dsn>"
    SENTRY_ENVIRONMENT: "stg-airbyte"```
I have also set these same environment variables specifically for the `worker` pod. I can see that these environment variables are present in the different pods (server, worker etc.). However, no errors are being reported in Sentry even though I have multiple sync jobs failing. Has anyone had any luck with getting the Sentry integration working with the Kubernetes deployment?

It's worth noting that the Sentry instance is self-hosted, so I suspect from the logs that the `allowedHosts` value only has `*.<http://sentry.io|sentry.io>`  configured, preventing it from talking to our Sentry instance.

<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/p1710507337565609) if you want to access the original thread.

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

<sub>
["sentry-integration", "airbyte-connectors", "kubernetes-deployment", "environment-variables", "allowedhosts"]
</sub>