Skip to content

Commit 62c13b2

Browse files
nevikashahnevikashah
committed
integrations removal changelog update
1 parent 7c0e00f commit 62c13b2

File tree

2 files changed

+92
-32
lines changed

2 files changed

+92
-32
lines changed

‎src/content/changelog/workers/2025-06-09-workers-integrations-changes.mdx‎

Lines changed: 17 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,45 +1,31 @@
11
---
2-
title: Workers integrations tab removed from dashboard
3-
description: As we evolve our integrations marketplace strategy, the Workers integrations tab has been removed from the Workers dashboard. Existing integrations continue to work, and new connections should be configured using Wrangler secrets.
2+
title: Workers native integrations were removed from the Cloudflare dashboard
3+
description: The Workers native integrations have been removed from the Workers dashboard. Existing integrations continue to work, and new connections should be configured using Wrangler secrets or the dashboard.
44
products:
55
- workers
66
date: 2025-06-09T19:00:00Z
7-
---
8-
9-
We are evolving our integrations marketplace strategy to better serve developers' needs. As part of this change, we have removed the database integrations tab from the Workers dashboard in favor of a more straightforward approach using [Wrangler secrets](/workers/wrangler/commands/#secret).
10-
11-
## Background
127

13-
Database integrations were [originally launched in May 2023](https://blog.cloudflare.com/announcing-database-integrations/) to connect to popular databases and observability providers with your Worker in just a few clicks.
8+
---
9+
Workers native integrations were [originally launched in May 2023](https://blog.cloudflare.com/announcing-database-integrations/) to connect to popular database and observability providers with your Worker in just a few clicks. We have since removed the integrations tab from the Workers dashboard, however, existing integrations remain functional.
1410

1511
## What's changed
16-
17-
- **Integrations tab removed**: The database integrations setup flow is no longer available in the Workers dashboard.
18-
- **Manual secret configuration**: New database connections should be configured by adding credentials as secrets to your Workers using `npx wrangler secret put` commands.
19-
- **Simplified workflow**: Developers now have direct control over their database credentials without needing to go through dashboard integration flows.
20-
12+
- **Integrations tab removed**: The integrations setup flow is no longer available in the Workers dashboard.
13+
- **Manual secret configuration**: New connections should be configured by adding credentials as secrets to your Workers using `npx wrangler secret put` commands.
2114

2215
## Impact on existing integrations
23-
24-
**Existing integrations will continue to work without any changes required.** If you have database integrations that were previously created through the dashboard, they will remain functional.
16+
**Existing integrations will continue to work without any changes required.** If you have integrations that were previously created through the dashboard, they will remain functional.
2517

2618
## Updating existing integrations
19+
If you'd like to modify your existing integration, you can update the secrets, environment variables, or [Tail Workers](/workers/observability/logs/tail-workers/) that were created from the original integration setup.
20+
- **Update secrets**: Use `npx wrangler secret put <SECRET_NAME>` to update credential values.
21+
- **Modify environment variables**: Update variables through the dashboard or Wrangler configuration.
22+
- **Dashboard management**: Access your Worker's settings in the [Cloudflare dashboard](https://dash.cloudflare.com) to modify connections created by our removed native integrations feature.
2723

28-
If you'd like to modify your existing integration, you can update the secrets, environment variables, or Tail Workers that were created from the original integration setup. Use the following approaches:
29-
30-
- **Update secrets**: Use `npx wrangler secret put <SECRET_NAME>` to update credential values
31-
- **Modify environment variables**: Update variables through the dashboard or Wrangler configuration
32-
- **Dashboard management**: Access your Worker's settings in the [Cloudflare dashboard](https://dash.cloudflare.com) to modify integration-created resources
33-
34-
## Setting up new database connections
35-
36-
For new database connections, refer to our [third-party database integrations documentation](/workers/databases/third-party-integrations/) for step-by-step guides on connecting to popular database providers including:
24+
If you have previously set up an observability integration with [Sentry](https://sentry.io), the following environment variables were set and are still modifiable:
25+
- `BLOCKED_HEADERS`: headers to exclude sending to Sentry
26+
- `EXCEPTION_SAMPLING_RATE`: number from 0 - 100, where 0 = no events go through to Sentry, and 100 = all events go through to Sentry
27+
- `STATUS_CODES_TO_SAMPLING_RATES`: a map of status codes -- like 400 or with wildcards like 4xx -- to sampling rates described above
3728

38-
- [Turso](/workers/databases/third-party-integrations/turso/)
39-
- [Neon](/workers/databases/third-party-integrations/neon/)
40-
- [Supabase](/workers/databases/third-party-integrations/supabase/)
41-
- [PlanetScale](/workers/databases/third-party-integrations/planetscale/)
42-
- [Upstash](/workers/databases/third-party-integrations/upstash/)
43-
- [Xata](/workers/databases/third-party-integrations/xata/)
29+
## Setting up new database and observability connections
30+
For new connections, refer to our step-by-step guides on connecting to popular database and observability providers including: [Sentry](/workers/observability/third-party-integrations/sentry), [Turso](/workers/databases/third-party-integrations/turso/), [Neon](/workers/databases/third-party-integrations/neon/), [Supabase](/workers/databases/third-party-integrations/supabase/), [PlanetScale](/workers/databases/third-party-integrations/planetscale/), [Upstash](/workers/databases/third-party-integrations/upstash/), [Xata](/workers/databases/third-party-integrations/xata/).
4431

45-
Each guide includes the exact `wrangler secret put` commands and environment setup needed to connect your Worker to the respective database service.

‎src/content/docs/workers/observability/third-party-integrations/sentry.mdx‎

Lines changed: 75 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
<<<<<<< HEAD
23
pcx_content_type: navigation
34
title: Sentry
45
external_link: https://docs.sentry.io/platforms/javascript/guides/cloudflare/
@@ -9,4 +10,77 @@ description: Connect to a Sentry project from your Worker to automatically send
910
---
1011

1112
Connect to a Sentry project from your Worker to automatically send
12-
errors and uncaught exceptions to Sentry.
13+
errors and uncaught exceptions to Sentry.
14+
=======
15+
pcx_content_type: concept
16+
title: Sentry
17+
head: []
18+
description: Connect to a Sentry project from your Worker to automatically send
19+
errors and uncaught exceptions to Sentry.
20+
sidebar:
21+
badge:
22+
text: Beta
23+
24+
---
25+
26+
import { Render } from "~/components"
27+
28+
[Sentry](https://sentry.io/welcome/) is an error tracking and performance monitoring platform that allows developers to diagnose, fix, and optimize the performance of their code.
29+
30+
This integration allows you to connect to a Sentry project from your Worker to automatically send errors and uncaught exceptions to Sentry with no code changes needed in the Workers application.
31+
32+
:::note
33+
34+
35+
Sentry integration is available to all Enterprise customers and Free, Pro, and Business customers on the [Workers Paid plan](/workers/platform/pricing/).
36+
37+
38+
:::
39+
40+
:::caution
41+
42+
43+
This integration is not supported for Pages projects. Pages does not support [Tail Workers](/workers/observability/logs/tail-workers/), and the Sentry integration relies on adding a Tail Worker to your Worker.
44+
45+
46+
:::
47+
48+
## How it works
49+
50+
This integration adds a [Tail Worker](/workers/observability/logs/tail-workers) to your application Worker. The Tail Worker automatically sends errors and uncaught exceptions to the Sentry project you have configured.
51+
52+
This integration supports the following Sentry features:
53+
54+
* **[Data Handling](https://develop.sentry.dev/sdk/data-handling/)**: As a best practice, do not include PII or other sensitive data in the payload sent to Sentry. HTTP headers (for example, `Authorization` or `Cookie`) can be removed before events are forwarded to Sentry.
55+
* **[Sampling](https://docs.sentry.io/platforms/javascript/configuration/sampling/#configuring-the-transaction-sample-rate)**: Sampling can be configured to manage the number and type of events sent to Sentry. Sampling rates can be configured based on the HTTP status code returned by the Worker and for uncaught exceptions. Setting the sampling rate to 100% sends all events to Sentry or setting it to 30% sends approximately 30% of events to Sentry.
56+
* **[Breadcrumbs](https://docs.sentry.io/product/issues/issue-details/breadcrumbs/)**: Breadcrumbs create a trail of events that happened prior to an issue. Breadcrumbs are automatically forwarded to Sentry in the case of an error or exception. These events consist of the `console.log()` from the Worker before the error or exception occurred.
57+
58+
:::note
59+
60+
If there are more configuration options that you would like to see, leave us feedback on the [Cloudflare Developer Discord](https://discord.cloudflare.com) (channel name: integrations).
61+
:::
62+
63+
## Set up an integration with Sentry
64+
65+
To set up an integration with Sentry, you need to have an existing Sentry project to connect to. [Create a Sentry project](https://docs.sentry.io/product/sentry-basics/integrate-frontend/create-new-project), or use an existing project for this integration. Then add the Sentry integration to your Worker.
66+
67+
To add the Sentry integration to your Worker:
68+
69+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
70+
2. Select **Workers & Pages**.
71+
3. In **Overview**, select your Worker.
72+
4. Select **Integrations** > **Sentry**.
73+
5. Follow the setup flow.
74+
75+
Once installed, the integration will automatically start forwarding matching events to Sentry. To learn more about Sentry, refer to [Sentry's official documentation](https://docs.sentry.io/).
76+
77+
<Render file="wrangler-tail-warning" />
78+
79+
:::caution
80+
81+
82+
Each Cloudflare account can only be linked to one Sentry organization. Use the [Sentry SDK](https://github.com/getsentry/sentry-javascript) in order to send events to projects in more than one Sentry organization.
83+
84+
85+
:::
86+
>>>>>>> 7961fa1835 (integrations removal changelog update)

0 commit comments

Comments
 (0)