Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

<@ULVA73B9P> using prefect3.13 what config should i configure to switch off "event feed" and saving all events data

:white_check_mark: thought for 86.2 seconds

Short answer: disable the event persister service. That stops saving events (and the Event Feed will be empty).

A couple of paths depending on where you run Prefect 3.13:

Self-hosted Prefect Server (OSS)
- Set this env var on the API/server service and restart it:
```
PREFECT_SERVER_SERVICES_EVENT_PERSISTER_ENABLED=false
```
- Or in a server config file:
```
server.services.event_persister.enabled = false
```
- Some deployments still use the older prefix; if you see “API” in your config, use:
```
PREFECT_API_SERVICES_EVENT_PERSISTER_ENABLED=false
```
- Docs: <https://docs-3.prefect.io/v3/api-ref/settings-ref|Settings reference> and <https://docs-3.prefect.io/v3/api-ref/python/prefect-server-events-services-event_persister|Event persister service>

Prefect Cloud
- You can’t turn off Cloud’s event persistence at the account level.
- If your goal is to stop emitting events from your runs, set the runtime to not send them (e.g., via an env var on your worker/flow). If you want, tell me how you’re running your flows (worker type, container, etc.) and I’ll give you the exact knob for your setup.

Can you confirm whether you’re on Cloud or self-hosted (and how you’re deploying the server/worker)? I’ll tailor the exact steps.