Activity Feed

ODD Platform records every metadata change as a typed event on a global Activity feed and on per-entity Activity tabs — the catalog's audit trail and change-driven discovery surface.

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.

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 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 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 was changed.

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.

Auto-resolved alert events

Auto-resolution events emitted from the Alerting 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 on Configure ODD Platform. 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.

• For per-entity user-authored discussion threads (a per-entity event stream complementary to this system-emitted one) → Data Collaboration.

• For the data-entity-group events that power the catalog's group view → Data Entity Groups & Domains.

• For the activity-feed partition setting → Configure ODD Platform → Activity-feed partitioning.