Skip to content

Commit 2f73183

Browse files
committed
Deletion request approval and API
1 parent 3ecd144 commit 2f73183

File tree

5 files changed

+56
-2
lines changed

5 files changed

+56
-2
lines changed

docs/api/data-deletion-rules.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
id: data-deletion-rules
3+
title: Data Deletion Rules APIs
4+
sidebar_label: Data Deletion Rules
5+
description: Data Deletion Rules APIs allow you to delete ingested data from Sumo Logic.
6+
---
7+
8+
import useBaseUrl from '@docusaurus/useBaseUrl';
9+
import ApiIntro from '../reuse/api-intro.md';
10+
import ApiRoles from '../reuse/api-roles.md';
11+
12+
<img src={useBaseUrl('img/icons/dashboards.png')} alt="icon" width="50"/>
13+
14+
The Data Deletion Rules allows you to quickly and easily request the removal of ingested data from Sumo Logic. This helps you with removal of inadvertently ingested sensitive data.
15+
16+
## Documentation
17+
18+
<ApiIntro/>
19+
20+
|Deployment|Documentation URL |
21+
|:----------|:-------------------|
22+
|AU |https://api.au.sumologic.com/docs/#tag/dataDeletionRules |
23+
|CA |https://api.ca.sumologic.com/docs/#tag/dataDeletionRules |
24+
|DE |https://api.de.sumologic.com/docs/#tag/dataDeletionRules |
25+
|EU |https://api.eu.sumologic.com/docs/#tag/dataDeletionRules |
26+
|FED |https://api.fed.sumologic.com/docs/#tag/dataDeletionRules |
27+
|JP |https://api.jp.sumologic.com/docs/#tag/dataDeletionRules |
28+
|KR |https://api.kr.sumologic.com/docs/#tag/dataDeletionRules |
29+
|US1 |https://api.sumologic.com/docs/#tag/dataDeletionRules |
30+
|US2 |https://api.us2.sumologic.com/docs/#tag/dataDeletionRules |
31+
32+
## Required role capabilities
33+
34+
<ApiRoles/>
35+
36+
* Review Deletion Requests
37+
* Manage Deletion Requests
38+
* View Deletion Requests

docs/manage/deletion-requests.md

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ Data cannot be recovered once it gets deleted. Ensure that you have appropriatel
5252
:::
5353
1. Select the **Time Range** when the data was ingested.
5454
1. When you're done, click **Save**.
55-
1. Your request will go to a Sumo Logic Customer Support Manager (CSM) for review and approval. You can check on your request in the **Status** column. <br/><img src={useBaseUrl('img/search/get-started-search/deletion-request-status.png')} alt="deletion request status" style={{border: '1px solid gray'}} width="400"/>
55+
1. Your request will go to your [Administrator for review and approval](#approve-the-deletion-request). You can check on your request in the **Status** column. <br/><img src={useBaseUrl('img/search/get-started-search/deletion-request-status.png')} alt="deletion request status" style={{border: '1px solid gray'}} width="400"/>
5656

5757
### From a Log Search
5858

@@ -88,12 +88,28 @@ To cancel a data deletion request:
8888

8989
<img src={useBaseUrl('img/search/get-started-search/deletion-request-cancel.png')} alt="screenshot showing how to cancel a deletion request" style={{border: '1px solid gray'}} width="800"/>
9090

91+
## Approve the deletion request
92+
93+
:::note
94+
- Ensure you have the **Administrator** access with **Review Deletion Requests** capability. By default, **Manage Deletion Requests** and **View Deletion Requests** capabilities will be added if you have the **Review Deletion Requests** capability.
95+
- Only **Administrator** will have the ability to view the **Approve** and **Reject** buttons.
96+
:::
97+
98+
Once the deletion request is created, it will be notified to your **Administrator** for approval. To approve or reject the request, follow the steps below:
99+
100+
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). Go to **Manage Data > Logs > Deletion Requests**.<br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu, select **Configuration**, and then under **Logs** select **Deletion Requests**.
101+
1. Filter for the status with **Pending review**. <img src={useBaseUrl('img/search/get-started-search/pending-requests.png')} alt="filter for pending deletion requests" style={{border: '1px solid gray'}} width="800"/>
102+
1. Click on the deletion request to review the request.
103+
1. **Approve** or **Reject** the request based on your requirement.
104+
- **Approve**. Enter **Delete** in the **Approve Deletion Request** pop-up to permanently delete the data, and click the **Approve Request** button. <br/><img src={useBaseUrl('img/search/get-started-search/approve-deletion-request.png')} alt="Approve deletion requests pop-up" style={{border: '1px solid gray'}} width="400"/>
105+
- **Reject**. Enter the reason for rejection in the **Reject Deletion Request** pop-up to help the requester understand the rejection issue to take necessary actions, and click the **Reject Request** button.<br/><img src={useBaseUrl('img/search/get-started-search/reject-deletion-request.png')} alt="Reject deletion requests pop-up" style={{border: '1px solid gray'}} width="400"/>
106+
91107
## Limitations
92108

93109
- Deletion requests will be processed one by one.
94110
- You can create upto 100 deletion requests at a time.
95111
- Each deletion request can include up to 1 petabyte (PB) of scanned data.
96-
- You can delete up to 1,000,000 messages per request.
112+
- You can delete up to 1,000,000 messages per request.
97113
- The maximum time range for each deletion request is one year.
98114
- Your system can support up to 10 active concurrent deletion tasks across different customers.
99115
- Ensure that the requests initiated are not deleting the data prior to `1st February 2024`. Any request before this timestamp will fail in creation.
178 KB
Loading
129 KB
Loading
150 KB
Loading

0 commit comments

Comments
 (0)