delete
Description
Using the delete
command marks all of the events returned by the search as deleted. Subsequent searches do not return the marked events. No user, not even a user with admin permissions, is able to view this data after deletion. The delete command does not reclaim disk space.
Removing data is irreversible. If you want to get your data back after the data is deleted, you must re-index the applicable data sources.
You cannot run the delete
command in a real-time search to delete events as they arrive.
Syntax
delete
Usage
The delete
command can be accessed only by a user with the "delete_by_keyword" capability. By default, only the "can_delete" role has the ability to delete events. No other role, including the admin role, has this ability. You should create a special userid that you log on with when you intend to delete indexed data.
To use the delete
command, run a search that returns the events you want deleted. Make sure that the search returns ONLY the events that you want to delete, and no other events. After you confirm that the results contain the data that you want to delete, pipe the search to the delete
command.
The delete
command does not trigger a roll of hot buckets to warm in the affected indexes.
The output of the delete
command is a table of the quantity of events removed by the fields splunk_server (the name of the indexer or search head), and index, as well as a rollup record for each server by index "__ALL__". The quantity of deleted events is in the deleted field. An errors field is also emitted, which will normally be 0.
Delete command restrictions
The delete
command does not work in all situations:
- Searches with centralized streaming commands.
- You cannot use the delete command after a centralized streaming command. For example, you can't delete events using a search like this:
index=myindex ... | head 100 | delete
- Centralized streaming commands include: head, streamstats, some modes of dedup, and some modes of cluster. See Command types.
- Events with an
index
field. - If your events contain a field named
index
aside from the defaultindex
field that is applied to all events. If your events do contain an additionalindex
field, you can useeval
before invokingdelete
, as in this example:
index=fbus_summary latest=1417356000 earliest=1417273200 | eval index = "fbus_summary" | delete
Permanently removing data from an index
The delete
command does not remove the data from your disk space. You must use the clean
command from the CLI to permanently remove the data. The clean
command removes all of the data in an index. You cannot select the specific data that you want to remove. See Remove indexes and indexed data in Managing Indexers and Clusters of Indexers.
Examples
1. Delete events with Social Security numbers
Delete the events from the insecure
index that contain strings that look like Social Security numbers. Use the regex
command to identify events that contain the strings that you want to match.
- Run the following search to ensure that you are retrieving the correct data from the
insecure
index.index=insecure | regex _raw = "\d{3}-\d{2}-\d{4}"
- If necessary, adjust the search to retrieve the correct data. Then add the
delete
command to the end of the search to delete the events.index=insecure | regex _raw = "\d{3}-\d{2}-\d{4}" | delete
2. Delete events that contain a specific word
Delete events from the imap
index that contain the word invalid
.
index=imap invalid | delete
3. Remove the Search Tutorial events
Remove all of the Splunk Search Tutorial events from your index.
- Login as a user with the
admin
role. - Click Settings, Access controls and create a new user with the
can_delete
role. - Log out as admin and log back in as the user with the
can_delete
role. - Set the time range picker to
All time
. - Run the following search to retrieve all of the Search Tutorial events.
source=tutorialdata.zip:*
- Confirm that the search is retrieving the correct data.
- Add the
delete
command to the end of the search criteria and run the search again.
The events are removed from the index.source=tutorialdata.zip:* | delete
- Log out as the user with the
can_delete
role.
dedup | delta |
This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10
Feedback submitted, thanks!