Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sentry Integration : Stop reporting all non system-error error types. #18133

Merged
merged 16 commits into from
Oct 18, 2022

Conversation

akashkulk
Copy link
Contributor

@akashkulk akashkulk commented Oct 18, 2022

Closes #18131

As part of the improving connector customer experience workstream, we want to emit config-error traces in discover/read (any place that can fail when a config can be changed) instead of throwing an exception and have that be a system-error by default.

These errors will now be attributed as config-errors with a relevant message to the user. As a result, we'd like to stop sending these to Sentry (which is currently only used for creating GH issues)

@github-actions github-actions bot added area/connectors Connector related issues area/platform issues related to the platform labels Oct 18, 2022
@github-actions
Copy link
Contributor

NOTE ⚠️ Changes in this PR affect the following connectors. Make sure to run corresponding integration tests:

  • source-mysql-strict-encrypt
  • destination-postgres
  • destination-postgres-strict-encrypt
  • source-redshift
  • destination-bigquery
  • destination-r2
  • source-mysql
  • source-clickhouse
  • source-tidb
  • source-mssql
  • source-cockroachdb-strict-encrypt
  • source-mongodb-v2
  • destination-mongodb
  • destination-databricks
  • source-db2
  • destination-clickhouse
  • source-alloydb-strict-encrypt
  • destination-elasticsearch
  • source-db2-strict-encrypt
  • destination-csv
  • destination-gcs
  • destination-mysql-strict-encrypt
  • destination-mysql
  • source-postgres
  • source-kafka
  • destination-mqtt
  • destination-kafka
  • destination-kinesis
  • destination-cassandra
  • destination-redshift
  • source-oracle-strict-encrypt
  • source-postgres-strict-encrypt
  • destination-rockset
  • source-relational-db
  • source-jdbc
  • destination-s3
  • source-e2e-test-cloud
  • source-sftp
  • destination-mariadb-columnstore
  • source-e2e-test
  • destination-oracle-strict-encrypt
  • destination-tidb
  • destination-azure-blob-storage
  • destination-oracle
  • source-bigquery
  • source-cockroachdb
  • source-scaffold-java-jdbc
  • destination-redis
  • source-mongodb-strict-encrypt
  • destination-e2e-test
  • destination-meilisearch
  • destination-pulsar
  • destination-mongodb-strict-encrypt
  • destination-dev-null
  • destination-elasticsearch-strict-encrypt
  • destination-pubsub
  • destination-snowflake
  • destination-jdbc
  • destination-bigquery-denormalized
  • source-oracle
  • destination-clickhouse-strict-encrypt
  • destination-local-json
  • destination-mssql-strict-encrypt
  • destination-mssql
  • source-snowflake
  • destination-keen
  • destination-dynamodb
  • source-elasticsearch
  • source-clickhouse-strict-encrypt
  • destination-scylla
  • source-mssql-strict-encrypt
  • source-alloydb

@evantahler
Copy link
Contributor

Closing #18132 in favor of this PR!

@github-actions
Copy link
Contributor

NOTE ⚠️ Changes in this PR affect the following connectors. Make sure to run corresponding integration tests:

  • source-tidb
  • source-alloydb
  • source-mssql-strict-encrypt
  • source-clickhouse-strict-encrypt
  • source-mysql-strict-encrypt
  • source-clickhouse
  • source-oracle-strict-encrypt
  • source-jdbc
  • source-scaffold-java-jdbc
  • source-oracle
  • source-postgres-strict-encrypt
  • source-snowflake
  • source-alloydb-strict-encrypt
  • source-mongodb-v2
  • source-db2-strict-encrypt
  • source-mongodb-strict-encrypt
  • source-bigquery
  • source-redshift
  • source-mysql
  • source-postgres
  • source-db2
  • source-cockroachdb-strict-encrypt
  • source-cockroachdb
  • source-mssql

@github-actions
Copy link
Contributor

NOTE ⚠️ Changes in this PR affect the following connectors. Make sure to run corresponding integration tests:

  • source-snowflake
  • source-clickhouse
  • source-jdbc
  • source-bigquery
  • source-mysql
  • source-alloydb-strict-encrypt
  • source-redshift
  • source-db2
  • source-mssql
  • source-mongodb-v2
  • source-cockroachdb-strict-encrypt
  • source-oracle
  • source-db2-strict-encrypt
  • source-oracle-strict-encrypt
  • source-scaffold-java-jdbc
  • source-mssql-strict-encrypt
  • source-postgres-strict-encrypt
  • source-tidb
  • source-postgres
  • source-cockroachdb
  • source-clickhouse-strict-encrypt
  • source-mysql-strict-encrypt
  • source-mongodb-strict-encrypt
  • source-alloydb

@akashkulk akashkulk temporarily deployed to more-secrets October 18, 2022 21:20 Inactive
@github-actions
Copy link
Contributor

NOTE ⚠️ Changes in this PR affect the following connectors. Make sure to run corresponding integration tests:

  • source-jdbc
  • source-mysql
  • source-bigquery
  • source-alloydb
  • source-mssql-strict-encrypt
  • source-redshift
  • source-mssql
  • source-scaffold-java-jdbc
  • source-oracle
  • source-mongodb-v2
  • source-mysql-strict-encrypt
  • source-mongodb-strict-encrypt
  • source-alloydb-strict-encrypt
  • source-postgres-strict-encrypt
  • source-cockroachdb-strict-encrypt
  • source-postgres
  • source-clickhouse-strict-encrypt
  • source-db2
  • source-oracle-strict-encrypt
  • source-tidb
  • source-db2-strict-encrypt
  • source-cockroachdb
  • source-clickhouse
  • source-snowflake

@github-actions github-actions bot removed the area/connectors Connector related issues label Oct 18, 2022
@akashkulk akashkulk temporarily deployed to more-secrets October 18, 2022 21:23 Inactive
Exclude list of unsupported failure reasons
@akashkulk akashkulk temporarily deployed to more-secrets October 18, 2022 21:45 Inactive
Copy link
Contributor

@pedroslopez pedroslopez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@akashkulk akashkulk marked this pull request as ready for review October 18, 2022 22:05
@akashkulk akashkulk temporarily deployed to more-secrets October 18, 2022 22:07 Inactive
@akashkulk akashkulk temporarily deployed to more-secrets October 18, 2022 22:11 Inactive
@akashkulk akashkulk temporarily deployed to more-secrets October 18, 2022 23:08 Inactive
Copy link
Contributor

@ryankfu ryankfu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for taking this on. If you can also add a brief description of what was changed and how come this PR existed outside of linking the Closes PR # that would be helpful if this PR needs to be referenced in the future

@akashkulk akashkulk merged commit 66e0055 into master Oct 18, 2022
@akashkulk akashkulk deleted the akash/sentry branch October 18, 2022 23:54
letiescanciano added a commit that referenced this pull request Oct 19, 2022
* master: (304 commits)
  Bump helm chart version reference to 0.40.27 (#18152)
  Bump helm chart version reference to 0.40.26 (#18094)
  Update deployment.yaml (#18151)
  Publishes Postgres, MySQL, MSSQL source with changes from #18041 (#18086)
  Fix minor DBT Cloud Errors. (#18147)
  Sentry Integration : Stop reporting all non system-error error types. (#18133)
  Docs: Fix backoff stategy docs (#18143)
  🐛 Destination GCS: Fix error logs to log 'Gcs' rather than 'AWS' (#17901)
  Add openAPI spec for Connector Builder Server (#17535)
  Alex/mvp UI for dbt cloud integration (#18095)
  increased timeout for sat tests (#18128)
  Bmoric/remove dep connector worker (#17977)
  `recordsRead` should be a long (#18123)
  doc_update_oath_issue_gsc (#17967)
  🎉 Source Zendesk Chat: engagements data fix infinity looping + gradlew format (#18121)
  🐛 Source Zendesk Chat: engagements data fix infinity looping (#17745)
  Custom APM Tracing (#17947)
  11679 BigQuery-Denormalized Destination: improve code coverage (#17827)
  increased timeout for sat tests (#18114)
  docs: clarify language (#18090)
  ...
jhammarstedt pushed a commit to jhammarstedt/airbyte that referenced this pull request Oct 31, 2022
…airbytehq#18133)

* Sentry Integration : Stop reporting all non system-error error types.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Only send non-config errors to Sentry
5 participants