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

[Docs] March 2024 Release Notes #36871

Merged
merged 24 commits into from
Apr 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -10,81 +10,74 @@ This page provides guidance on how to manage notifications for Airbyte, allowing

| Type of Notification | Description |
|------------------------|---------------------------------------------------------------------------------------------------------------------|
| Failed Syncs | A sync from any of your connections fails. Note that if sync runs frequently or if there are many syncs in the workspace these types of events can be noisy |
| Successful Syncs | A sync from any of your connections succeeds. Note that if sync runs frequently or if there are many syncs in the workspace these types of events can be noisy
| Automated Connection Updates | A connection is updated automatically (ex. a source schema is automatically updated) |
| Connection Updates Requiring Action | A connection update requires you to take action (ex. a breaking schema change is detected) |
| Warning - Repeated Failures | A connection will be disabled soon due to repeated failures. It has failed 50 times consecutively or there were only failed jobs in the past 7 days |
| Sync Disabled - Repeated Failures | A connection was automatically disabled due to repeated failures. It will be disabled when it has failed 100 times consecutively or has been failing for 14 days in a row |
| Warning - Upgrade Required (Cloud only) | A new connector version is available and requires manual upgrade |
| Sync Disabled - Upgrade Required (Cloud only) | One or more connections were automatically disabled due to a connector upgrade deadline passing
| **Failed Syncs** | A sync from any of your connections fails. Note that if sync runs frequently or if there are many syncs in the workspace these types of events can be noisy |
| **Successful Syncs** | A sync from any of your connections succeeds. Note that if sync runs frequently or if there are many syncs in the workspace these types of events can be noisy
| **Automated Connection Updates** | A connection is updated automatically (ex. a source schema is automatically updated) |
| **Connection Updates Requiring Action** | A connection update requires you to take action (ex. a breaking schema change is detected) |
| **Warning - Repeated Failures** | A connection will be disabled soon due to repeated failures. It has failed 50 times consecutively or there were only failed jobs in the past 7 days |
| **Sync Disabled - Repeated Failures** | A connection was automatically disabled due to repeated failures. It will be disabled when it has failed 100 times consecutively or has been failing for 14 days in a row |
| **Warning - Upgrade Required** (Cloud only) | A new connector version is available and requires manual upgrade |
| **Sync Disabled - Upgrade Required** (Cloud only) | One or more connections were automatically disabled due to a connector upgrade deadline passing

### Enabling schema update notifications

To be notified of any source schema changes, make sure you have enabled `Automatic Connection Updates` and `Connection Updates Requiring Action` notifications. If these are off, even if you turned on schema update notifications in a connection's settings, Airbyte will *NOT* send out any notifications related to these types of events.

To edit this setting, click **Connections** and select the connection you want to receive notifications for. Click the **Settings** tab on the Connection page. In the **Advanced Settings**, toggle **Schema update notifications**.


## Configure Email Notification Settings

<AppliesTo cloud />

To set up email notifications:
To set up email notifications, click **Settings** and navigate to **Workspace** > **Notifications**.

1. In the Airbyte UI, click **Settings** and navigate to **Notifications**.
Toggle which messages you'd like to receive from Airbyte. All email notifications will be sent by default to the creator of the workspace.

2. Toggle which messages you'd like to receive from Airbyte. All email notifications will be sent by default to the creator of the workspace. To change the recipient, edit and save the **notification email recipient**. If you would like to send email notifications to more than one recipient, you can enter an email distribution list (ie Google Group) as the recipient.

3. Click **Save changes**.
![](./assets/notifications-email.png)

:::note
All email notifications except for Successful Syncs are enabled by default.
:::

## Configure Slack Notification settings
### Modify the email recipient
To change the recipient, edit and save the **notification email recipient**. If you would like to send email notifications to more than one recipient, you can enter an email distribution list (ie Google Group) as the recipient.

To set up Slack notifications:
## Configure Slack Notification settings

If you're more of a visual learner, just head over to [this video](https://www.youtube.com/watch?v=NjYm8F-KiFc&ab_channel=Airbyte) to learn how to do this. You can also refer to the Slack documentation on how to [create an incoming webhook for Slack](https://api.slack.com/messaging/webhooks).
If you're more of a visual learner, head over to [this video](https://www.youtube.com/watch?v=NjYm8F-KiFc&ab_channel=Airbyte) to learn how to do this. You can also refer to the Slack documentation on how to [create an incoming webhook for Slack](https://api.slack.com/messaging/webhooks).

### Create a Slack app

1. **Create a Slack App**: Navigate to https://api.slack.com/apps/. Select `Create an App`.
1. To set up Slack notifications, navigate to https://api.slack.com/apps/. Select `Create an App`.

![](../../.gitbook/assets/notifications_create_slack_app.png)
![](./assets/notification-slack-create-app.png)

2. Select `From Scratch`. Enter your App Name (e.g. Airbyte Sync Notifications) and pick your desired Slack workspace.

3. **Set up the webhook URL.**: in the left sidebar, click on `Incoming Webhooks`. Click the slider button in the top right to turn the feature on. Then click `Add New Webhook to Workspace`.
3. **Enable Incoming Webhooks**: in the left sidebar, click on `Incoming Webhooks`. Click the slider button in the top right to turn the feature on. Then click `Add New Webhook to Workspace`.

![](../../.gitbook/assets/notifications_add_new_webhook.png)
![](./assets/notification-slack-add-webhook.png)

4. Pick the channel that you want to receive Airbyte notifications in (ideally a dedicated one), and click `Allow` to give it permissions to access the channel. You should see the bot show up in the selected channel now. You will see an active webhook right above the `Add New Webhook to Workspace` button.
4. Select the channel that you want to receive Airbyte notifications in (ideally a dedicated one), and click `Allow` to give it permissions to access the channel. You should see the bot show up in the selected channel now. You will see an active webhook right above the `Add New Webhook to Workspace` button.

![](../../.gitbook/assets/notifications_webhook_url.png)
![](./assets/notification-slack-webhook-url-success.png)

5. Click `Copy.` to copy the link to your clipboard, which you will need to enter into Airbyte.

Your Webhook URL should look something like this:

![](../../.gitbook/assets/notifications_airbyte_notification_settings.png)
Your Webhook URL should look similar to this:

```
https://hooks.slack.com/services/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PM1
```

### Enable the Slack notification in Airbyte

1. In the Airbyte UI, click **Settings** and navigate to **Notifications**.

2. Paste the copied webhook URL to `Webhook URL`. Using a Slack webook is recommended. On this page, you can toggle each slider decide whether you want notifications on each notification type.

3. **Test it out.**: you can click `Test` to send a test message to the channel. Or, just run a sync now and try it out! If all goes well, you should receive a notification in your selected channel that looks like this:

![](../../.gitbook/assets/notifications_slack_message.png)

You're done!

4. Click **Save changes**.

## Enable schema update notifications
1. Click **Settings** and navigate to **Notifications**. On this page, you can toggle each slider decide whether you want notifications on each notification type. Paste the copied webhook URL to `Webhook URL`.

To be notified of any source schema changes:
1. Make sure you have enabled `Automatic Connection Updates` and `Connection Updates Requiring Action` notifications. If these are off, even if you turned on schema update notifications in a connection's settings, Airbyte will *NOT* send out any notifications related to these types of events.
3. **Test it out**: you can click `Test` to send a test message to the channel. Or, just run a sync now and try it out! For a successful sync, you should receive a notification that looks like this:

2. In the Airbyte UI, click **Connections** and select the connection you want to receive notifications for.
![](./assets/notification-slack-success.png)

3. Click the **Settings** tab on the Connection page.

4. Toggle **Schema update notifications**.
4. Click **Save changes** to ensure you continue to receive alerts about your Airbyte syncs.
16 changes: 6 additions & 10 deletions docs/cloud/managing-airbyte-cloud/manage-credits.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,15 +8,15 @@ Airbyte [credits](https://airbyte.com/pricing) are used to pay for Airbyte resou

## Buy credits

To purchase credits directly through the UI,
1. To purchase credits directly through the UI, click **Billing** in the left-hand sidebar. The billing page displays the available credits, total credit usage, and the credit usage per connection.

1. Click **Billing** in the left-hand sidebar.
:::tip

2. If you are unsure of how many credits you need, use our [Cost Estimator](https://www.airbyte.com/pricing) or click **Talk to Sales** to find the right amount for your team.
If you are unsure of how many credits you need, use our [Cost Estimator](https://www.airbyte.com/pricing) or click **Talk to Sales** to find the right amount for your team.

3. Click **Buy credits**.
:::

4. Determine the quantity of credits you intend to purchase. Adjust the **credit quantity**. When you're ready, click **Checkout**.
2. Click **Buy credits**. Enter the quantity of credits you intend to purchase and adjust the **credit quantity** accordingly. When you're ready, click **Checkout**.

:::note

Expand All @@ -30,11 +30,7 @@ To purchase credits directly through the UI,

5. You'll be renavigated to a Stripe payment page. If this is your first time purchasing, you'll be asked for payment details. After you enter your billing address, sales tax (if applicable) is calculated and added to the total.

6. Click **Pay**.

Your payment is processed. The Billing page displays the available credits, total credit usage, and the credit usage per connection.

A receipt for your purchase is sent to your email.
6. Click **Pay** to process your payment. A receipt for your purchase is automatically sent to your email.

:::note

Expand Down
20 changes: 2 additions & 18 deletions docs/cloud/managing-airbyte-cloud/manage-data-residency.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,15 +18,7 @@ While the data is processed in a data plane of the chosen residency, the cursor

When you set the default data residency, it applies your preference to new connections only. If you do not adjust the default data residency, the [Airbyte Default](configuring-connections.md) region is used (United States). If you want to change the data residency for an individual connection, you can do so in its [connection settings](configuring-connections.md).

To choose your default data residency:

1. In the Airbyte UI, click **Settings**.

2. Click **Data Residency**.

3. Click the dropdown and choose the location for your default data residency.

4. Click **Save changes**.
To choose your default data residency, click **Settings** in the Airbyte UI. Navigate to **Workspace** > **Data Residency**. Use the dropdown to choose the location for your default data residency and save your changes.

:::info

Expand All @@ -37,15 +29,7 @@ Depending on your network configuration, you may need to add [IP addresses](/ope
## Choose the data residency for a connection
You can additionally choose the data residency for your connection in the connection settings. You can choose the data residency when creating a new connection, or you can set the default data residency for your workspace so that it applies for any new connections moving forward.

To choose a custom data residency for your connection:

1. In the Airbyte UI, click **Connections** and then click the connection that you want to change.

2. Click the **Settings** tab.

3. Click the **Data residency** dropdown and choose the location for your default data residency.

4. Click **Save changes**
To choose a custom data residency for your connection, click **Connections** in the Airbyte UI and then select the connection that you want to configure. Navigate to the **Settings** tab, open the **Advanced Settings**, and select the **Data residency** for the connection.

:::note

Expand Down
32 changes: 32 additions & 0 deletions docs/release_notes/march_2024.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# March 2024
## airbyte v0.51.0 to v0.56.0

This page includes new features and improvements to the Airbyte Cloud and Airbyte Open Source platforms.

## ✨ Highlights

Airbyte now supports **OpenID Connect (OIDC) SSO** for Airbyte Enterprise and Airbyte Cloud Teams. This enables companies to use Airbyte with Entra ID/AD via the OIDC protocol.

Airbyte certified our [Microsoft SQL Server source](/integrations/sources/mssql) to support terabyte-sized tables, expanded datetime data types, and reliability improvements.

Airbyte migrated our [Redshift destination](https://github.com/airbytehq/airbyte/pull/36255) to the [Destinations V2](./upgrading_to_destinations_v2) framework. This enables you to map tables one-to-one with your source, experience better error handling (particularly with large records), and deliver data incrementally.


## Platform Releases

In addition to our OpenID Connect support, we also released:

- A major upgrade to our Docker and Helm deployments, which simplifies how external logs are configured. Learn more about the specific changes in our [migration guide](/deploying-airbyte/on-kubernetes-via-helm#migrate-from-old-chart-to-airbyte-v0520-and-latest-chart-version).

- A breaking change to Docker deployments. Containers no longer run as the `root` user. If you are upgrading from an older version, the `airbyte_workspace` docker volume must be recreated to fix the ownership of staging directories under `/tmp` (in the container). Alternatively, you can manually update the ownership (`airbyte:airbyte`) of the directory mount point /tmp/workspace in all containers where `airbyte_workspace` is mounted (see: `docker-compose.yaml`)

- Our major version upgrades (Airbyte Cloud only) now only require manual upgrading when you are actively syncing a stream that has changed. Otherwise, syncs will continue as is and the version will be upgraded automatically for you.

## Connector Improvements

In addition to our MS-SQL certification, we also released a few notable Connector improvements:

- We released several connector builder enhancements, including support for raw YAML blocks, modification the start date when testing, and added the ability to adjust page/slice/record limits. We also resolved bugs in page size and interpolation inputs, improved the switching time between YAML and UI, and fixed several layout issues.
- Our [Bing source](https://github.com/airbytehq/airbyte/pull/35812) includes the following new streams: `Audience Performance Report`, `Goals And Funnels Report`, `Product Dimension Performance Report`
- Our [JIRA source](https://github.com/airbytehq/airbyte/pull/35656) now contains more fields to the following streams: `board_issues`,`filter_sharing`,`filters`,`issues`, `permission_schemes`, `sprint_issues`,`users_groups_detailed` and `workflows`
- Our [Snapchat Source](https://github.com/airbytehq/airbyte/pull/35660) now contains additional fields in the `ads`, `adsquads`, `creatives`, and `media` streams.
2 changes: 1 addition & 1 deletion docs/using-airbyte/core-concepts/namespaces.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ products: all

Namespaces are used to generally organize data, separate tests and production data, and enforce permissions. In most cases, namespaces are schemas in the database you're replicating to.

As a part of connection setup, you select where in the destination you want to write your data. Note: The default configuration is **Destination default**.
As a part of connection setup, you select where in the destination you want to write your data. Note: The default configuration is **Destination-defined**.

| Destination Namespace | Description |
| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
Expand Down
4 changes: 4 additions & 0 deletions docs/using-airbyte/core-concepts/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,10 @@ For more details, see our [dbt integration documentation](/cloud/managing-airbyt

A workspace is a grouping of sources, destinations, connections, and other configurations. It lets you collaborate with team members and share resources across your team under a shared billing account.

## Organization

Organizations let you collaborate with team members and share workspaces across your team.

## Glossary of Terms

You can find a extended list of [Airbyte specific terms](https://glossary.airbyte.com/term/airbyte-glossary-of-terms/), [data engineering concepts](https://glossary.airbyte.com/term/data-engineering-concepts) or many [other data related terms](https://glossary.airbyte.com/).