Hi 👋 We are trying to setup the Sentry Integration for Airbyte Connectors, but fail to see which is the appropriate way to do so. We are running Airbyte

v0.40.29

on Kubernetes, using Helm charts

v0.43.22-helm

, and tried adding the following environment variables for

worker

deployments: •

SENTRY_DSN: <dsn>

, as documented in: ◦ https://docs.airbyte.com/operator-guides/configuring-airbyte#worker ◦ https://docs.airbyte.com/operator-guides/sentry-integration/ •

JOB_ERROR_REPORTING_STRATEGY: sentry

and

JOB_ERROR_REPORTING_SENTRY_DSN: <dsn>

as hinted in: ◦ https://github.com/airbytehq/airbyte/issues/7957#issuecomment-1297672827 ◦ https://github.com/airbytehq/airbyte/issues/18755 ◦ https://airbytehq.slack.com/archives/C021JANJ6TY/p1681193093461609 ◦ https://github.com/airbytehq/airbyte-platform/blob/main/airbyte-config/config-models/src/main/java/io/airbyte/config/EnvConfigs.java ◦ https://github.com/airbytehq/airbyte-platform/blob/main/airbyte-config/config-models/src/main/java/io/airbyte/config/Configs.java • adding

SENTRY_ENVIRONMENT: <env>

to the mix ◦ though, this variable is not referenced anywhere in the Airbyte / Airbyte Platform codebase Here is the relevant excerpt from our `values.yaml`:

worker:
  extraEnv:
    - name: JOB_ERROR_REPORTING_STRATEGY
      value: "SENTRY"
    - name: JOB_ERROR_REPORTING_SENTRY_DSN
      valueFrom:
        secretKeyRef:
          name: airbyte-sentry-dsn
          key: dsn

The values are properly set for

worker

deployments and pods, but are not set by the

worker

when scheduling and instantiating

jobs

pods with source and destination connector containers. Has anyone been able to setup Sentry with Airbyte running on Kubernetes?

A message from kapa.ai