You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/zombie-flags.mdx
+13-13Lines changed: 13 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ title: Zombie Flags
4
4
description: This page explains how to identify and manage Zombie Flags in ConfigCat through the dashboard, email reports, or the Zombie Flags API.
5
5
---
6
6
7
-
Zombie flags are feature flags that are no longer needed or actively used. They often remain in the codebase long after their purpose has been fulfilled. Removing these outdated flags can reduce technical debt, improve performance, and simplify your codebase.
7
+
Zombie flags (stale flags) are feature flags that are no longer needed or actively used. They often remain in the codebase long after their purpose has been fulfilled. Removing these outdated flags can reduce technical debt, improve performance, and simplify your codebase.
8
8
9
9
Common scenarios where zombie flags appear:
10
10
@@ -34,9 +34,9 @@ There are three ways to access and manage Zombie flags in ConfigCat:
34
34
The [Zombie flags page](https://app.configcat.com/product/zombie-flags) shows all the stale flags in a table for the selected product based on the filters set:
35
35
36
36
-**Inactivity**: How long the flag was inactive for.
37
-
-**Feature flag scope**: All flags or only ones that are watched by you.
38
-
-**Included environments**: The ConfigCat [environment](https://configcat.com/docs/main-concepts/#environment)for which you want to analyze flags.
39
-
-**Ignored flags based on tags**: The flags to exclude based on their tags.
37
+
-**Feature flag scope**: Choose between all feature flags or only those you are watching.
38
+
-**Included environments**: The ConfigCat [environment(s)](https://configcat.com/docs/main-concepts/#environment)to include in the analysis.
39
+
-**Ignored flags based on tags**: Exclude flags based on assigned tags.
40
40
-**Stale in all/any selected environments**: Choose whether to include flags that are stale in all or any of the selected environments.
41
41
-**Filter by config or feature flag name**: Type at least the first letter of the feature flag or config name to auto-filter the results.
42
42
@@ -50,14 +50,14 @@ If you have the [Code References](https://configcat.com/docs/advanced/code-refer
50
50
51
51
### Using the Zombie Flags Report Email
52
52
53
-
The Zombie Flags Report scans your ConfigCat dashboard and sends an email report of the feature flags that haven't been updated or toggled within a specified time frame.
53
+
The Zombie Flags Report scans your ConfigCat dashboard and sends an email report of the feature flags that haven't been updated or toggled within the configured timeframe.
54
54
55
-
You could customize the report to include only the flags you want to track, similar to filtering in the dashboard.
55
+
You can customize the report to include only the flags you want to track, using filters similar to those available in the dashboard.
56
56
57
57
#### How to Set Up the Zombie Feature Flags Report
58
58
59
59
1. Log in to the [ConfigCat dashboard](https://app.configcat.com/my-account/zombie-flags-report).
60
-
2. Click the Organization name in the top-right corner.
60
+
2. Click the Organization name in the top-left corner.
61
61
3. Select **My Zombie Flags Report** from the dropdown menu.
62
62
63
63
<imgalt="Navigating to My Zombie Flags Report"src="/docs/assets/guide/my-zombie-flags-report/navigating-to-my-zombie-flags-report_192dpi.png"width="1366"height="768"decoding="async"loading="lazy" />
@@ -66,15 +66,15 @@ You could customize the report to include only the flags you want to track, simi
66
66
67
67
The email report could be customized as follows:
68
68
69
-
-**Receive report via email:**Toggle this option to enable the email report, and specify how often you'd like to receive the report (e.g., daily, weekly, or monthly).
69
+
-**Receive report via email:**Turn on email notifications and set the frequency (daily, weekly, monthly).
70
70
71
71
-**Criteria:** Define how long a flag must be inactive before it's marked as stale.
72
72
73
-
-**Scope:**Choose to include all feature flags or only the ones you're watching.
73
+
-**Scope:**Include all flags or only watched ones.
74
74
75
-
-**Environment:**Select the ConfigCat [environment](https://configcat.com/docs/main-concepts/#environment)for which you want to analyze flags.
75
+
-**Environment:**Choose the ConfigCat [environment(s)](https://configcat.com/docs/main-concepts/#environment) you want to analyze.
76
76
77
-
-**Tags:**Select the flags you want to ignore in the report based on their tags.
77
+
-**Tags:**Exclude specific flags based on tags.
78
78
79
79
-**Stale in all/any selected environments:** Choose whether to include flags that are stale in all or any of the selected environments.
80
80
@@ -88,9 +88,9 @@ Here's a preview of what the Zombie Flags report email looks like:
88
88
89
89
### Using the Zombie Flags API
90
90
91
-
The [Zombie Flags API](https://api.configcat.com/docs/index.html#tag/Zombie-(stale)-flags) allows you to access your zombie flags using an API endpoint programmatically.
91
+
The [Zombie Flags API](https://api.configcat.com/docs/index.html#tag/Zombie-(stale)-flags) allows programmatic access to zombie flag data. This is useful for integrating flag cleanup processes into your CI/CD workflows or internal tooling.
92
92
93
-
Here's a preview of what it looks like in Postman:
93
+
You can use tools like Postman to retrieve zombie flag data via the API for testing or integration. Here's a preview of what it looks like in Postman:
94
94
95
95
<imgalt="Using the Zombie Flags API in Postman"src="/docs/assets/guide/my-zombie-flags-report/using-the-zombie-flags-api-in-postman_192dpi.png"width="1366"height="768"decoding="async"loading="lazy" />
0 commit comments