Title: Management and Monitoring
Locale: en
URL: https://sensorswave.com/en/docs/feature-gates/management-and-monitoring/
Description: Learn how to effectively manage Feature Gates
This article explains how to effectively manage Feature Gates, including viewing the gate list, status management, report data, and change history.

## Feature Gate list

### Accessing the list

1. Log in to the Sensors Wave console
2. Click **Feature Gates** in the left menu
3. View all Feature Gates in the list

### List information

The list displays the following information:

| Column | Description |
|--------|-------------|
| **Gate name** | The identifier used in code |
| **Display name** | A user-friendly display name |
| **Status** | Draft, Debugging, Running, Released, Finished |
| **Covered users** | Number of users currently matching rules |
| **Last updated** | Last modification time |
| **Created by** | The user who created the Feature Gate |

### Filtering and searching

#### Filter by status

- **All**: Show all gates
- **Draft**: Show only unpublished gates
- **Debugging**: Show only gates in debug mode
- **Running**: Show only active gates
- **Released**: Show only completed gates
- **Finished**: Show only finished gates

#### Search

Search by gate name or display name.

### Sorting

Sort by the following fields:

- **Created time** (default)
- **Updated time**
- **Gate name**
- **Covered user count**

## Feature Gate details

### Accessing the detail page

Click a Feature Gate in the list to enter its detail page.

### Detail page tabs

#### Overview

Displays the Feature Gate's basic information and current configuration:

- Gate identifier
- Description and creation info
- Default value
- Rule list
- Current status

#### Data

Displays the Feature Gate's report data, including cumulative traffic statistics and time trends. See the [Report data](#report-data) section below.

#### History

Displays the complete history of all configuration changes. See the [Change history](#change-history) section below.

#### Settings

Manage advanced settings for the Feature Gate.

## Status management

### Status descriptions

Feature Gates have 5 possible statuses:

| Status | Description |
|--------|-------------|
| **Draft** | Gate has been created but not published — has no effect on users |
| **Debugging** | Gate is in debug mode for internal testing |
| **Running** | Gate is published and active |
| **Released** | Gate has completed its release process; feature runs stably |
| **Finished** | Gate lifecycle has ended; feature is fully launched or retired |

### Status transition flow

```
Draft → Debugging → Running → Released → Finished
```

### Start debugging

Switch a draft gate to debug mode:

1. Go to the Feature Gate detail page
2. Verify the configuration is correct
3. Click **Debug**
4. The gate enters debug mode for internal testing

### Start running

Switch a debugging gate to running:

1. Go to the Feature Gate detail page
2. Confirm the debug results meet expectations
3. Click **Run**
4. The gate starts taking effect for users

### Release the gate

Mark a running gate as released:

1. Go to the Feature Gate detail page
2. Confirm the feature is running stably
3. Click **Release**
4. The gate is marked as released

### Finish the gate

Mark a released gate as finished:

1. Go to the Feature Gate detail page
2. Confirm the feature is fully launched or retired
3. Click **Finish**
4. The gate lifecycle ends

**When to finish**:
- The feature is fully released and no longer needs gradual control
- The feature has been removed from the codebase
- Confirmed the gate is no longer needed

### Delete the gate

Permanently delete a Feature Gate:

1. Go to the Feature Gate detail page
2. Go to the **Settings** tab
3. Click **Delete Feature Gate**
4. Enter the gate name to confirm
5. The Feature Gate is permanently deleted

> **Warning**: Deletion is irreversible. Proceed with caution. It's recommended to move the gate to Finished status first and delete only after confirming it's no longer needed.

## Report data

Feature Gates provide detailed report data to help you understand actual usage and traffic distribution.

### Accessing report data

1. Go to the Feature Gate detail page
2. Click the **Data** tab
3. View the report data

### Basic information

The top of the report page shows the Feature Gate's basic information:

| Field | Description |
|-------|-------------|
| **Run duration** | The time range since the Feature Gate started running, for example: 2026-01-22 - Present |
| **Rule count** | The number of rules currently configured |

### Cumulative traffic statistics

The cumulative traffic table shows the traffic distribution for each variant:

| Field | Description |
|-------|-------------|
| **Variant** | The allocation result (Pass or Fail) |
| **Cumulative traffic** | The cumulative number of exposures for this variant |
| **Cumulative traffic ratio** | This variant's share of total traffic |

**Example data**:

| Variant | Cumulative traffic | Cumulative ratio |
|---------|-------------------|-----------------|
| Pass | 2,043 | 50.99% |
| Fail | 1,964 | 49.01% |
| **Total** | **4,007** | **100.00%** |

### Cumulative traffic time trend

The page includes a cumulative traffic time trend chart that lets you:

- **Observe traffic changes**: View how traffic changes over time
- **Verify allocation ratios**: Confirm whether actual allocation matches the configured expectations
- **Identify anomalies**: Detect sudden spikes or drops in traffic

### Uses of report data

- **Verify configuration**: Confirm that allocation ratios are working as expected
- **Monitor usage**: Understand the actual coverage of the Feature Gate
- **Troubleshoot issues**: Identify potential problems through traffic trends
- **Support decisions**: Use data to decide whether to expand the rollout percentage

## Change history

### Viewing history

Go to the **History** tab on the Feature Gate detail page to view all configuration changes.

### Record contents

Each record contains:

| Field | Description |
|-------|-------------|
| **Change #** | The change sequence number |
| **Operation type** | Create, update, debug, etc. |
| **Updated time** | When the operation occurred |
| **Updated by** | The user who performed the operation |

## Best practices

### Regular review

**Recommended frequency**: Monthly

**Review checklist**:
- [ ] Check for gates that have been in draft or debug status for too long
- [ ] Check whether covered user counts are abnormal
- [ ] Check for gates that haven't been used in a long time
- [ ] Move fully released Feature Gates to Finished status promptly
- [ ] Update gate descriptions and documentation

### Naming conventions

Unified naming conventions make management easier:

- Use module prefixes: `recommendation_`, `payment_`, `user_`
- Use descriptive names: `new_algorithm`, `wechat_pay_enabled`
- Avoid abbreviations: use `recommendation` instead of `recom`

For details, see [Best Practices - Naming Conventions](best-practices.mdx#naming-conventions).

### Documentation

Maintain clear documentation for each Feature Gate:

- **Description field**: Detailed explanation of the gate's purpose
- **Code comments**: Explain the gate's function in the codebase

## Next steps

Now that you understand how to manage Feature Gates, you can:

1. **[Best Practices](best-practices.mdx)**: Master the best ways to use Feature Gates
2. **[FAQ](faq.mdx)**: Find answers to common questions

---

**Last updated**: January 28, 2026