# Activity Feed Track changes to your data entities by monitoring the global **Activity** page or the **Activity** tab on a data entity's detail page. Every metadata edit the platform observes — entity lifecycle transitions, ownership changes, tag and term assignments, dataset-field edits, alerts — emits a typed event onto the feed. The feed is the catalog's audit trail and the change-driven discovery surface: who did what to which entity, and when. ![](/files/FGiluwwMOYraX6fccjPd) ## Where to find it * **Global Activity page** — top-level `Activity` entry in the platform's navigation. Shows every event across the catalog with a seven-facet filter panel (see below). * **Per-entity Activity tab** — every data-entity detail page has an `Activity` tab that scopes the feed to events on that entity only (plus a few additional internal event types — entity overview / metadata / schema / relation updates and custom-metadata create / update / delete — that are recorded on the per-entity tab but hidden from the global filter to keep that view concise). ## Filters on the global Activity page The Filters panel on the Activity page lets you narrow the feed by seven facets: * **Calendar** — restrict to a date / date-range window. * **Datasource** — limit to events on entities from a specific datasource. * **Namespace** — limit to events on entities in a given namespace. * **Event type** — pick a single event type from the enumeration in the next subsection (e.g. `OWNERSHIP_CREATED`, `OPEN_ALERT_RECEIVED`). * **Tag** — show events on entities carrying one or more selected tags (multi-select). * **Owner** — show events on entities with one or more selected owners (multi-select). Useful for "what happened to my team's data this week". * **User** — show events performed by one or more selected users (multi-select). Useful for auditing a specific person's platform activity. ## Event types The **Event type** filter on the global Activity page exposes the following event types, grouped here by the area of the metadata they describe. **Data entity lifecycle** * `DATA_ENTITY_CREATED` – a data entity was created in the platform. * `DATA_ENTITY_STATUS_UPDATED` – an entity's status changed (`UNASSIGNED`, `DRAFT`, `STABLE`, `DEPRECATED`, `DELETED`). This is the event to filter on to find entity deletions — there is no separate "deleted" event type. * `BUSINESS_NAME_UPDATED` – the business name of an entity was edited. * `DESCRIPTION_UPDATED` – the description of an entity was edited. **Ownership** * `OWNERSHIP_CREATED` – an owner was added to a data entity. * `OWNERSHIP_UPDATED` – an owner's role on a data entity was changed. * `OWNERSHIP_DELETED` – an owner was removed from a data entity. **Tags and terms** * `TAG_ASSIGNMENT_UPDATED` – tags on a data entity were added, removed, or changed. * `TERM_ASSIGNMENT_UPDATED` – terms linked to a data entity were added, removed, or changed. **Dataset fields (columns)** * `DATASET_FIELD_VALUES_UPDATED` – enum values configured on a dataset field were edited. * `DATASET_FIELD_DESCRIPTION_UPDATED` – a field's description was edited. * `DATASET_FIELD_INTERNAL_NAME_UPDATED` – a field's internal (user-defined) name was edited. * `DATASET_FIELD_TAGS_UPDATED` – tags on a dataset field were added, removed, or changed. * `DATASET_FIELD_TERM_ASSIGNMENT_UPDATED` – terms linked to a dataset field were added, removed, or changed. **Data entity groups** * `CUSTOM_GROUP_CREATED` – a custom [data entity group](/features/data-discovery/groups-domains.md) was created. * `CUSTOM_GROUP_UPDATED` – the members or metadata of a custom group were changed. **Alerts** * `OPEN_ALERT_RECEIVED` – a new alert was opened for a data entity. Driven by the [Alerting](/features/active-platform-features/alerting.md) subsystem. * `RESOLVED_ALERT_RECEIVED` – an existing alert was resolved. * `ALERT_STATUS_UPDATED` – the status of an alert was changed manually. * `ALERT_HALT_CONFIG_UPDATED` – the [per-entity alert halt configuration](/features/active-platform-features/alerting.md#halt-notifications-per-entity) was changed. {% hint style="info" %} The platform emits a few additional internal event types (entity overview / metadata / schema / relation updates, custom metadata create / update / delete) that are recorded on the entity's own Activity tab but are intentionally hidden from the global Activity filter to keep the feed concise. {% endhint %} ## Auto-resolved alert events Auto-resolution events emitted from the [Alerting](/features/active-platform-features/alerting.md) subsystem are recorded as system events on the feed (no operator identity attached); manually-resolved alerts carry the operator's identity. This lets a reader walking the feed distinguish between alerts that were worked on by a human and alerts that simply cleared themselves on the next ingest. ## Configuration Activity-feed retention and partitioning are controlled by the platform-level setting [`odd.activity.partition-period`](/configuration-and-deployment/odd-platform.md#activity-feed-partitioning-odd-activity-partition-period) on [Configure ODD Platform](/configuration-and-deployment/odd-platform.md). Adjust the partitioning cadence per the volume your deployment generates — the operator-side reference is the canonical home for this key. ## Where to next * For the alert events that source four of the feed's event types → [Alerting](/features/active-platform-features/alerting.md). * For per-entity user-authored discussion threads (a per-entity event stream complementary to this system-emitted one) → [Data Collaboration](/features/active-platform-features/data-collaboration.md). * For the data-entity-group events that power the catalog's group view → [Data Entity Groups & Domains](/features/data-discovery/groups-domains.md). * For the activity-feed partition setting → [Configure ODD Platform → Activity-feed partitioning](/configuration-and-deployment/odd-platform.md#activity-feed-partitioning-odd-activity-partition-period). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.opendatadiscovery.org/features/active-platform-features/activity-feed.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.