Core conceptsTesting and monitoring
Events help you keep track of changes across your Unleash instance. You can explore events in Event Log or using the global Event Timeline.
The Event Log provides a full list of all events, whereas the Event Timeline offers a highlight of recent key events and Signals from external sources. You can use Event Log for auditing purposes, while Event Timeline is particularly helpful for debugging recent changes and their impact.
The Event Log lists all events in your Unleash instance. You can search and filter events by date range, event type, project, feature flag, and user. You can also export events as CSV or JSON files.
To access events in the Admin UI, you need Admin access. To view all events, go to Admin settings > Event log. To view events for a specific feature flag, go to the Event log tab on that feature flag’s page.
Each event type contains different data, but all events follow the same schema:
Fields marked with an asterisk (*) are always returned in the event schema. Other fields may be optional or have null values, depending on the event type.
See the feature-created event type for an example event.
The IP address in events shows the IP address of the user who performed the action.
Event Timeline highlights recent events across all your projects in one unified timeline. You can access the timeline from the top menu in the Admin UI.

The timeline shows key events and signals for up to 48 hours per environment and is designed to help you get an overview of changes and quickly identify and debug any issues. You can switch between different time spans to focus on recent activity. Although you can filter events by environment, the timeline also shows environment-agnostic events, such as archiving a feature flag.
You can enable or disable the timeline view at any time based on your preferences. Events that occur close together in time are automatically grouped, but hovering over an event group shows detailed information about the specific events.
Events related to feature flags and their life cycle.
feature-createdGenerated when you create a feature flag. The data property contains the details for the new feature flag.
feature-deletedGenerated when you delete a feature flag. The preData property contains the deleted feature flag data.
feature-archivedGenerated when you archive a feature flag. preData and data are null.
feature-revivedGenerated when you revive an archived feature flag. preData and data are null.
feature-metadata-updatedGenerated when a feature flag’s metadata, such as description, flag type, or impression data settings, are changed. The data property contains the new flag data. The preData property contains the flag’s previous data.
feature-project-changeGenerated when you move a feature flag from one project to another. The data property contains the names of the old and the new project.
feature-importGenerated when you import a feature flag as part of an import process. The data property contains the feature flag data. See feature-created for an example.
feature-taggedGenerated when you add a tag to a feature flag. The data property contains the new tag.
feature-untaggedGenerated when you remove a tag from a feature flag. The data property contains the tag that was removed. See feature-tagged for an example.
feature-tag-importGenerated when you import a tagged feature flag as part of an import job. The data property contains the name of the feature and the tag.
feature-strategy-addGenerated when you add a strategy to a feature flag. The data property contains the configuration for the new strategy.
feature-strategy-updateGenerated when you update a feature flag strategy. The data property contains the new strategy configuration. The preData property contains the previous strategy configuration.
feature-strategy-removeGenerated when you remove a strategy from a feature flag. The preData contains the configuration of the strategy that was removed.
feature-stale-onGenerated when you mark a feature flag as stale. preData and data are null.
feature-stale-offGenerated when you mark a stale feature flag as no longer stale. preData and data are null.
feature-environment-enabledGenerated when you enable an environment for a feature flag. The environment property contains the name of the environment, preData and data are null.
feature-environment-disabledGenerated when you disable an environment for a feature. The environment property contains the name of the environment. preData and data are null.
drop-featuresGenerated when you delete existing features as part of an import job. The data.name property is "all-features".
drop-feature-tagsGenerated when you drop all existing tags as part of a configuration import. The data.name is "all-feature-tags". See drop-features for an example.
feature-potentially-stale-onGenerated when Unleash marks a feature flag as potentially stale due to exceeding the expected lifetime of its feature flag type. preData and data are null.
feature-updatedDeprecated functionality
Deprecated in Unleash 4.3. Use more granular events, such as feature-strategy-update, instead.
strategy-createdGenerated when you create a strategy. The data property contains the strategy configuration.
strategy-updatedGenerated when you change a strategy’s configuration. The data property contains the new strategy configuration. See strategy-created for an example.
strategy-deletedGenerated when you delete a strategy. The data property contains the name of the deleted strategy, preData is null.
strategy-deprecatedGenerated when you deprecate a strategy. The data property contains the name of the deprecated strategy, preData is null.
strategy-reactivatedGenerated when you reactivate a deprecated strategy. The data property contains the name of the reactivated strategy, preData is null.
strategy-importGenerated when you import a strategy as part of an import job. The data property contains the strategy’s configuration, preData is null. See strategy-created for an example.
drop-strategiesGenerated when you delete existing strategies as part of an import job. The data.name property is "all-strategies".
context-field-createdGenerated when you create a context field. The data property contains the context field configuration.
context-field-updatedGenerated when you update a context field. The data property contains the new context field configuration. See context-field-created for an example.
context-field-deletedGenerated when you delete a context field. The data property contains the name of the deleted context field.
project-createdGenerated when you create a project. The data property contains the project configuration.
project-updatedGenerated when you update a project’s configuration. The data property contains the new project configuration. The preData property contains the previous project configuration.
project-deletedGenerated when you delete a project. The project property contains the name of the deleted project.
project-importGenerated when you import a project. The data property contains the project’s configuration details. See project-created for an example.
drop-projectsGenerated when you delete existing projects as part of an import job. The data.name property is "all-projects".
tag-createdGenerated when you create a new tag. The data property contains the tag that was created.
tag-deletedGenerated when you delete a tag. The data property contains the tag that was deleted. See tag-created for an example.
tag-importGenerated when you import a tag as part of an import job. The data property contains the imported tag. See tag-created for an example.
drop-tagsGenerated when you delete existing tags as part of an import job. The data.name property is "all-tags".
tag-type-createdGenerated when you create a new tag type. The data property contains the tag type configuration.
tag-type-updatedGenerated when you update a tag type. The data property contains the new tag type configuration. See tag-type-created for an example.
tag-type-deletedGenerated when you delete a tag type. The data property contains the name of the deleted tag type.
tag-type-importGenerated when you import a tag type as part of an import job. The data property contains the imported tag. See tag-type-created for an example.
drop-tag-typesGenerated when you drop all existing tag types as part of a configuration import. The data.name property is "all-tag-types".
addon-config-createdGenerated when you create an integration configuration. The data property contains the provider type.
addon-config-updatedGenerated when you update an integration configuration. The data property contains the id and provider of the integration.
addon-config-deletedGenerated when you delete an integration configuration. The data property contains the id of the integration.
user-createdGenerated when you create a new user. The data property contains the user’s information.
user-updatedGenerated when you update a user. The data property contains the updated user information; the preData property contains the previous state of the user’s information.
user-deletedGenerated when you delete a user. The preData property contains the deleted user’s information.
environment-importGenerated when you import an environment as part of an import job. The data property contains the configuration of the imported environment.
drop-environmentsGenerated when you delete existing environments as part of an import job. The data.name property is "all-environments".
segment-createdGenerated when you create a segment. The data property contains the newly created segment.
segment-updatedGenerated when you update a segment’s configuration. The data property contains the new segment configuration; the preData property contains the previous segment configuration.
segment-deletedGenerated when you delete a segment. preData property contains the deleted segment.