Meta Event Deletion Tool
1. Overview
The event_del_full Meta Event Deletion Tool deletes all historical data and event definitions for one or more events in a specified project. It also deletes the associations between those events and their properties, along with the definitions and property associations of related Meta Events. Property definitions themselves are retained.
Use this tool when you need to completely remove event data and definitions. It does not support deleting only part of the data by time range or other conditions.
Deletion cannot be undone. Confirm the deletion scope in advance and back up data as needed. Deleting an event does not stop it from being reported. If data continues to be reported or backfilled, the event and its data may reappear.
2. Instructions
2.1 Before you begin
These instructions apply to private deployment environments with the secondary development tool installed. Before proceeding, prepare the target project's appid and the names of the events to delete, and confirm the following:
- Reporting has stopped for the target events, and you have checked for any pending or backfill data.
- You have assessed the impact on related analyses, reports, and Meta Events.
- If ETL (the data processing service) needs to be stopped, you have scheduled an appropriate maintenance window. Stopping ETL may affect data processing for other projects.
If you are unsure whether your environment supports this command or cannot assess these impacts, contact your administrator or technical support first.
2.2 Start the tool
Log in to a server where the secondary development tool is installed and configured, and use an account with permission to run it. For deployments that use the ta account, log in as root, run su - ta, and then start the tool:
ta-tool event_del_full
No additional parameters are required at startup. Follow the prompts. While the tool is waiting for input, enter quit to exit. To cancel after deletion has started, see "3.3 Cancel deletion".
2.3 Enter the appid and confirm the project
When prompted to enter the appId, enter the target project's appid. After validation, the tool displays the project name. Check it carefully and enter y to continue. Any other input cancels the operation.
If the tool reports that no project matches the appId, check the appid and run the command again.
2.4 Enter the event names
The tool prompts you to enter the event names, separated by commas. Enter the event names (keys) used for reporting, not their display names .
Separate multiple events with a standard comma , or a full-width comma ,, for example:
draw_card, gold_get
Duplicate event names are automatically removed. If no valid event name is entered, the tool prompts you to enter the names again.
2.5 Confirm what will be deleted
The tool displays the project name, the list of events to delete, and the deletion scope, and requests two consecutive confirmations . After checking the details, enter y both times to continue. Any other input at either prompt cancels the operation.
2.6 Choose whether to stop ETL
The tool prompts: "Stop ETL before deleting? <y/n> >":
- Enter y: ETL is stopped before deletion. Afterward, the tool automatically attempts to restart ETL. Data processing on the affected nodes is interrupted while ETL is stopped, which may also affect other projects.
- Enter n: ETL remains running, and the tool asks you to confirm the risk. You must ensure that no related event data is reported during the operation. Enter
yonly after confirming this condition; any other input cancels the operation. - Enter anything else: The operation is canceled.
In K8s (containerized) environments, you must choose to stop ETL. If you choose not to stop it, the tool reports that this mode is unsupported and exits. You must run the command again.
Stopping ETL does not stop clients from reporting data or clear data that has not yet been processed. Check reporting and backfill activity before proceeding, regardless of which option you choose.
2.7 Wait for execution and check the results
After confirmation, the tool checks the events and environment status, waits for any necessary background synchronization tasks to finish, and then deletes the events one by one. If any specified event does not exist, the task stops before deletion begins.
The tool displays progress for each event, followed by counts and lists of successful and failed deletions. Use these lists to verify the results. If you cancel midway, also check for events that have not yet been processed.
Depending on your selection, the tool automatically requests a cache refresh or attempts to restart ETL. No manual call is needed. Wait for the command to exit and check for any subsequent errors. A successful event deletion does not mean that the data processing service has been successfully restored. If cache refresh or ETL recovery fails, save the terminal output and contact your administrator or technical support.
3. Notes
3.1 Deletion scope and related impacts
| Content | How it works |
|---|---|
| All historical data for the specified events, including updated event data | Deleted, without a time range restriction |
| Definitions of the specified events and their property associations | Delete |
| Definitions of related Meta Events and their property associations | Delete |
| Property definitions | Retained |
| User data, project information, and project members | Not deleted |
| Data and definitions of events not specified | Not deleted directly; shared Meta Events may be affected |
If multiple events are associated with the same Meta Event, deleting one of them may also delete the shared Meta Event definition and property associations, affecting the use of other events. If such associations exist, contact your administrator or technical support to assess the impact first.
The tool does not automatically adjust analyses, reports, or other configurations that reference deleted events. Check these dependencies in advance and update them as needed after deletion.
3.2 Common messages and actions
| Message or symptom | How it works |
|---|---|
| Waiting for background data synchronization tasks to finish before deletion | The tool waits and retries automatically. If there is no progress for an extended period, contact your administrator or technical support. |
| Maintenance is in progress; metadata modification is prohibited during this period | Run the command after maintenance finishes. If you are unsure of the current status, contact your administrator. |
| The event does not exist in the project | Check the project appid and event name. Make sure you entered the event name rather than its display name, and that the event has not already been deleted. |
| Event metadata changed while waiting for the lock; deletion has been canceled | Recheck the events and their associations in the project, confirm the deletion scope, and run the command again. |
| Some events failed to delete; check the logs | Save the failed event list and error information. After troubleshooting, follow "3.4 Handle deletion failures". |
3.3 Cancel deletion
After execution starts, press Ctrl+C once to request cancellation, and wait for the tool to finish cleanup. Canceling does not restore data that has already been deleted. The event currently being processed may also have been partially deleted.
Do not press Ctrl+C repeatedly or forcibly terminate the process, as this may interfere with ETL recovery. If service recovery errors appear after cancellation, save the terminal output and contact your administrator or technical support.
3.4 Handle deletion failures
If deletion fails for one event, the tool normally continues with subsequent events. Some data for the failed event may already have been deleted, and completed deletions are not automatically reversed.
Save the lists of successful and failed events and the error information, and contact your administrator or technical support for troubleshooting. When retrying, enter only events that still exist and still need to be deleted. Do not resubmit the entire original list if it includes events that were successfully deleted, as a missing event may cause the task to stop.
If all events were successfully deleted and only cache refresh or ETL recovery failed, resolve the corresponding service issue. There is no need to delete the events again.

