Docs for exclude_beat_tasks (#6995)

* Docs for `exclude_beat_tasks`

---------

Co-authored-by: Shana Matthews <shana.l.matthews@gmail.com>

Author: antonpirker

src/platform-includes/crons/setup/python.celery.mdx

@@ -51,6 +51,32 @@ You don't need to create Cron Monitors for your tasks on Sentry.io, we'll do it
 
 </Note>
 
+### Excluding Celery Beat Tasks from Auto Discovery
+
+You can exclude Celery Beat tasks from being auto-instrumented. To do this, add a list of tasks you want to exclude as option `exclude_beat_tasks` when creating `CeleryIntegration`. The list can contain simple strings with the full task name, as specified in the Celery Beat schedule, or regular expressions to match multiple tasks.
+
+```python
+    exclude_beat_tasks = [
+        "some-task-a",
+        "payment-check-.*",
+    ]
+
+    sentry_sdk.init(
+        dsn='___PUBLIC_DSN___',
+        integrations=[
+            CeleryIntegration(
+                monitor_beat_tasks=True,
+                exclude_beat_tasks=exclude_beat_tasks),
+            ],
+        environment="local.dev.grace",
+        release="v1.0",
+    )
+```
+
+In this example the task `some-task-a` and all tasks with a name starting with `payment-check-` will be ignored.
+
+For more information, see the documentation for <PlatformLink to="/#options">options on CeleryIntegration</PlatformLink>.
+
 ## Manual Task Monitoring
 
 We provide a lightweight decorator to make monitoring individual tasks easier. To use it, add `@sentry_sdk.monitor` to your Celery task (or any function), then supply a `monitor_slug` of a monitor created previously on Sentry.io. Once this is done, every time the task (or function) is executed, telemetry data will be captured when a task is started, when it finishes, and when it fails.

src/platforms/python/guides/celery/index.mdx

@@ -67,3 +67,49 @@ Sentry uses custom message headers for distributed tracing. For Celery versions
 The fix for the custom headers propagation issue was introduced to Celery project ([PR](https://github.com/celery/celery/pull/6374)) starting with version 5.0.1. However, the fix was not backported to versions 4.x.
 
 </Alert>
+
+## Options
+
+To set options on `CeleryIntegration` to change its behavior, add it explicitly to your `sentry_sdk.init()`:
+
+```python
+import sentry_sdk
+from sentry_sdk.integrations.celery import CeleryIntegration
+
+sentry_sdk.init(
+    dsn="___PUBLIC_DSN___",
+    # ...
+    integrations=[
+        CeleryIntegration(
+            monitor_beat_tasks=True,
+            exclude_beat_tasks=["unimportant-task", "payment-check-.*"],
+        ),
+    ],
+)
+```
+
+You can pass the following keyword arguments to `CeleryIntegration()`:
+
+- `propagate_traces`
+
+  Propagate Sentry tracing information to the Celery task. This makes it possible to link errors in Celery tasks to the function that triggered the Celery task. If this is set to `False`, errors in Celery tasks can't be matched to the triggering function.
+
+  The default is `True`.
+
+- `monitor_beat_tasks`:
+
+  Turn auto-instrumentation on or off for Celery Beat tasks using Sentry Crons.
+
+  See <PlatformLink to="/crons/#celery-beat-auto-discovery">Celery Beat Auto Discovery</PlatformLink> to learn more.
+
+  The default is `False`.
+
+- `exclude_beat_tasks`:
+
+  A list of Celery Beat tasks that should be excluded from auto-instrumentation using Sentry Crons. Only applied if `monitor_beat_tasks` is set to `True`.
+
+  The list can contain strings with the names of tasks in the Celery Beat schedule to be excluded. It can also include regular expressions to match multiple tasks. For example, if you include `"payment-check-.*"` every task starting with `payment-check-` will be excluded from auto-instrumentation.
+
+  See <PlatformLink to="/crons/#celery-beat-auto-discovery">Celery Beat Auto Discovery</PlatformLink> to learn more.
+
+  The default is `None`.