The audit log and history tabs
Read time: 6 minutes
Last edited: Mar 07, 2024
Overview
This topic explains how to use the Audit log and History tabs to track changes made in LaunchDarkly.
Using the audit log
The unlimited audit log is available to customers on a Pro or Enterprise plan. For Starter plans, the audit log is restricted to the last 30 days of events. To learn more, read about our pricing. To upgrade your plan, contact Sales.
The Audit log is a running tally of changes made to feature flags in a given environment. You can access the audit log from the sidenav.
The audit log displays changes to feature flags for your current environment only. To view the changes for other environments, use the Switch environment menu at the top of your sidenav.
By default, the audit log displays the most recent ten entries. Use the Show: menu to change the date range of entries the audit log displays. Use the search box to find specific audit log entries. You can search for the full or partial name of the resource.
Here is an image of the audit log with the "Show" menu called out:
Click the Details button for more information about each change. JSON patch changes include representations of the JSON patch operation, and a diff from the old and new JSON, if available.
You can also use the REST API: Audit log
To learn more about using the audit log with the REST API, read How to filter audit log entries using a resource specifier.
Using the history tabs
The user interface (UI) also contains a History tab on the Account settings page, as well as on the pages for individual feature flags, segments, teams, members, and other resources. Each History tab contains a record of the changes made in LaunchDarkly to those resources.
On the History tab for the flag, segment, team, and members pages, use the Actions: menu to filter for specific actions.
The audit log for account changes is available to customers on an Enterprise plan. To learn more, read about our pricing. To upgrade your plan, contact Sales.
Actions recorded in the Audit log and History tabs
The Audit log and History tabs record each action taken on a flag. A particular entry may include one or more actions.
In the LaunchDarkly UI, the Audit log and History tabs display a description of each action or set of actions, as entered by the member who performed them. If you use the REST API to review the audit log, the API response also includes a list of the specific actions.
The following sections describe the actions that the Audit log and History tabs record. On the History tabs for flags, segments, teams, and members, you can use the Actions: menu to filter for specific actions.
Expand for actions related to targeting changes
The following table includes the actions related to targeting changes that are recorded in the Audit log and History tabs. Unless otherwise specified, these actions affect only the current environment:
| Action on flag | Name in REST response | Description |
|---|---|---|
| Update fallthrough | updateFallthrough | Update the default rule, also called the "fallthrough" rule. |
| Update flag variations | updateFlagVariations | Change the flag's variations. This action affects all environments in a project. |
| Update feature workflows | updateFeatureWorkflows | Change a flag's feature workflows. |
| Update global archived | updateGlobalArchived | Change whether a flag is archived. This action affects all environments in a project. |
| Update off variation | updateOffVariation | Update the variation returned when the flag is toggled off. |
| Update on | updateOn | Toggle a flag's targeting on or off. |
| Update prerequisites | updatePrerequisites | Update flag prerequisites. |
| Update rules | updateRules | Update custom targeting rules. |
| Update scheduled changes | updateScheduledChanges | Change the scheduled updates on a feature flag. |
| Update targets | updateTargets | Update individual context targeting rules. |
Expand for actions related to flag settings
The following table includes the actions related to flag settings that are recorded in the Audit log and History tabs. Each of these actions affect all environments in a project:
| Action on flag | Name in REST response | Description |
|---|---|---|
| Create flag | createFlag | Create a flag. |
| Delete flag | deleteFlag | Delete a flag. |
| Update client-side flag availability | updateClientSideFlagAvailability | Change whether the flag is available to client-side SDKs. |
| Update description | updateDescription | Change the description of a flag. |
| Update flag custom properties | updateFlagCustomProperties | Update custom properties attached to a flag. |
| Update flag default variations | updateFlagDefaultVariations | Change the default flag variations used by newly-created environments for a flag. |
| Update include in snippet | updateIncludeInSnippet | Change whether the feature flag is available to front-end code with the JavaScript SDK. |
| Update name | updateName | Change the name of a flag. |
| Update tags | updateTags | Update tags associated with a flag. |
| Update temporary | updateTemporary | Mark a flag temporary or permanent. |
Expand for actions related to environment-specific settings
The following table includes the actions related to environment-specific settings that are recorded in the Audit log and History tabs:
| Action on flag | Name in REST response | Description |
|---|---|---|
| Create triggers | createTriggers | Create a new trigger. |
| Delete triggers | deleteTriggers | Delete a trigger. |
| Update flag salt | updateFlagSalt | Update a flag's salt. |
| Update track events | updateTrackEvents | Change whether to send detailed event information for a flag in a given environment. |
| Update triggers | updateTriggers | Update an existing trigger. |
Expand for actions related to collaboration
The following table includes the actions related to collaboration that are recorded in the Audit log and History tabs:
| Action on flag | Name in REST response | Description |
|---|---|---|
| Apply approval request | applyApprovalRequest | Apply an approved approval request for a flag. |
| Bypass required approval | bypassRequiredApproval | Bypass required approvals in the environment. |
| Create approval request | createApprovalRequest | Create an approval request for a flag. |
| Create flag link | createFlagLink | Create a flag link. This affects all environments in a project. |
| Delete approval request | deleteApprovalRequest | Delete an approval request for a flag. |
| Delete flag link | deleteFlagLink | Delete a flag link. This affects all environments in a project. |
| Manage flag followers | manageFlagFollowers | Manage the list of members who receive flag change notifications. |
| Review approval request | reviewApprovalRequest | Review an approval request for a flag. |
| Update maintainer | updateMaintainer | Update the flag maintainer. This affects all environments in a project. |
| Update flag link | updateFlagLink | Update a flag link. This affects all environments in a project. |
Expand for actions related to other flag changes
The following table includes the actions related to other flag changes that are recorded in the Audit log and History tabs:
| Action on flag | Name in REST response | Description |
|---|---|---|
| Clone flag | cloneFlag | Create a new flag with settings based on an existing flag. This affects all environments in a project. |
| Copy flag config from | copyFlagConfigFrom | Copy settings from a flag. |
| Copy flag config to | copyFlagConfigTo | Copy settings to a flag. |
| Update expiring targets | updateExpiringTargets | Change a flag's expiring individual context targeting rules. |
| Update flag rule description | updateFlagRuleDescription | Update the description for custom targeting rules. |