Skip to content

Commit 24fa45b

Browse files
JV0812jpipkin1kimsauceatishya-22
authored
Deletion request approval and API update (#5680)
* Deletion request approval and API * Update docs/manage/deletion-requests.md * Update docs/manage/deletion-requests.md * Update docs/manage/deletion-requests.md * Update docs/manage/deletion-requests.md * Update deletion-requests.md * minor fix * Update data-deletion-rules.md * Update docs/manage/deletion-requests.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update docs/api/data-deletion-rules.md Co-authored-by: Kim (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: Kim (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: Kim (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: Kim (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: Kim (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: Kim (Sumo Logic) <[email protected]> * Update docs/manage/deletion-requests.md Co-authored-by: Atishya Gupta <[email protected]> * Update docs/manage/deletion-requests.md * minor fix * ss updated --------- Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> Co-authored-by: Kim (Sumo Logic) <[email protected]> Co-authored-by: Atishya Gupta <[email protected]>
1 parent d740566 commit 24fa45b

File tree

6 files changed

+66
-2
lines changed

6 files changed

+66
-2
lines changed

docs/api/data-deletion-rules.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
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+
<head>
9+
<meta name="robots" content="noindex" />
10+
</head>
11+
12+
<p><a href="/docs/beta"><span className="beta">Beta</span></a></p>
13+
14+
import useBaseUrl from '@docusaurus/useBaseUrl';
15+
import ApiIntro from '../reuse/api-intro.md';
16+
import ApiRoles from '../reuse/api-roles.md';
17+
18+
<img src={useBaseUrl('img/icons/dashboards.png')} alt="icon" width="50"/>
19+
20+
Data Deletion Rules allow you to quickly and easily request the removal of ingested data from Sumo Logic. This helps you with removal of inadvertently ingested sensitive data.
21+
22+
## Documentation
23+
24+
<ApiIntro/>
25+
26+
|Deployment|Documentation URL |
27+
|:----------|:-------------------|
28+
|AU |https://api.au.sumologic.com/docs/#tag/dataDeletionRules |
29+
|CA |https://api.ca.sumologic.com/docs/#tag/dataDeletionRules |
30+
|DE |https://api.de.sumologic.com/docs/#tag/dataDeletionRules |
31+
|EU |https://api.eu.sumologic.com/docs/#tag/dataDeletionRules |
32+
|FED |https://api.fed.sumologic.com/docs/#tag/dataDeletionRules |
33+
|JP |https://api.jp.sumologic.com/docs/#tag/dataDeletionRules |
34+
|KR |https://api.kr.sumologic.com/docs/#tag/dataDeletionRules |
35+
|US1 |https://api.sumologic.com/docs/#tag/dataDeletionRules |
36+
|US2 |https://api.us2.sumologic.com/docs/#tag/dataDeletionRules |
37+
38+
## Required role capabilities
39+
40+
<ApiRoles/>
41+
42+
* Review Deletion Requests
43+
* Manage Deletion Requests
44+
* View Deletion Requests

docs/manage/deletion-requests.md

Lines changed: 22 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,7 @@ After a data deletion request is approved, data will be deleted from the organiz
3434
:::note
3535
- During the data deletion process, existing messages may temporarily appear duplicated for a few seconds. These duplicated messages will automatically disappear once the data deletion is complete.
3636
- Pinned queries may continue to display data identified for deletion for up to 24 hours from the initial run, prior to the data deletion request approval.
37+
- Data deletion requests are automatically canceled after 30 days if no action is taken.
3738
:::
3839

3940
:::info
@@ -52,7 +53,11 @@ Data cannot be recovered once it gets deleted. Ensure that you have appropriatel
5253
:::
5354
1. Select the **Time Range** when the data was ingested.
5455
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"/>
56+
1. An email about your request will be sent to 50 most recently active approval users with [approval access](#approve-the-deletion-request). You can check on your request in the **Status** column.
57+
:::note
58+
If you require an approval apart from this 50 users, you can forward the deletion request approval email to the required users.
59+
:::
60+
<img src={useBaseUrl('img/search/get-started-search/deletion-request-status.png')} alt="deletion request status" style={{border: '1px solid gray'}} width="400"/>
5661

5762
### From a Log Search
5863

@@ -88,12 +93,27 @@ To cancel a data deletion request:
8893

8994
<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"/>
9095

96+
## Approve the deletion request
97+
98+
:::note
99+
To approve or reject a request, ensure you have the **Review Deletion Requests** [role capability](/docs/manage/users-roles/roles/role-capabilities/). By default, **Manage Deletion Requests** and **View Deletion Requests** capabilities will be added if you have the **Review Deletion Requests** capability.
100+
:::
101+
102+
Once the deletion request is created, an email notification will be sent to the users who have approval access. To approve or reject the request, follow the steps below:
103+
104+
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 Sumo Logic main menu select **Data Management**, and then under **Logs** select **Deletion Requests**.
105+
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"/>
106+
1. Click the deletion request to review it.
107+
1. **Approve** or **Reject** the request based on your requirement.<br/><img src={useBaseUrl('img/search/get-started-search/approve-reject-deletion-request.png')} alt="Approve/Reject deletion requests side panel" style={{border: '1px solid gray'}} width="400"/>
108+
- **Approve**. Enter **Delete** in the **Approve Deletion Request** pop-up to permanently delete the data, and click the **Delete Data** 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"/>
109+
- **Reject**. Enter the reason for rejection in the **Reject Deletion Request** pop-up to help the requester understand the reason for rejection and take any 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"/>
110+
91111
## Limitations
92112

93113
- Deletion requests will be processed one by one.
94114
- You can create upto 100 deletion requests at a time.
95115
- 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.
116+
- You can delete up to 1,000,000 messages per request.
97117
- The maximum time range for each deletion request is one year.
98118
- Your system can support up to 10 active concurrent deletion tasks across different customers.
99119
- Ensure that the requests initiated are not deleting the data prior to `1st February 2024`. Any request before this timestamp will fail in creation.
63.4 KB
Loading
128 KB
Loading
129 KB
Loading
150 KB
Loading

0 commit comments

Comments
 (0)