Skip to content

Commit 6ccb0a8

Browse files
committed
Minor content fix
1 parent fbeb95f commit 6ccb0a8

File tree

1 file changed

+18
-9
lines changed

1 file changed

+18
-9
lines changed

docs/manage/manage-subscription/usage-management.md

Lines changed: 18 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
88

99
This page provides information about the Scan Budgets, which allows you to define spending limits for queries to prevent unexpected charges. This will help you manage Sumo Logic credits, especially in pay-per-use scenarios, by setting budgets on scan data volume.
1010

11-
Sumo Logic provides two ways with which you can set the query limits:
11+
Sumo Logic provides two modes with which you can set the query limits:
1212
- Basic
1313
- Advanced
1414

@@ -17,7 +17,7 @@ Sumo Logic provides two ways with which you can set the query limits:
1717
To manage the query size limit using **Basic** configuration:
1818

1919
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Administration > Account > Usage Management**. <br/> [**New UI**](/docs/get-started/sumo-logic-ui/). In the top menu, select **Administration**, and then under **Account**, select **Usage Management**. You can also click the **Go To...** menu at the top of the screen and select **Usage Management**. <br/><img src={useBaseUrl('/img/manage/account/usage-management.png')} alt="usage-management" style={{border:'1px solid gray'}} width="650"/>
20-
1. **Enable Query Limit**. Select this checkbox and click on **Update limit** to enter the GB value based on your needs. Sumo Logic recommends a GB value per query as per the 95th percentile to be within the safe limits. You can also check the query size of the last 10 queries by clicking on **Click here** to help you determine the appropriate size limit. If you leave this checkbox unchecked, no limits will be added to the query. However, if you run an unoptimized query, excessive data will be scanned and accordingly the scan cost will be increased.
20+
1. **Enable Query Limit**. Select this checkbox and click on **Update limit** to enter the GB value based on your needs. Sumo Logic recommends a GB value per query as per the 95th percentile to be within the safe limits. You can also check the query size of the last 10 queries by clicking on **Click here** to help you determine the appropriate size limit. If you leave this checkbox unchecked, no limits will be added to the query.
2121
1. Click **Save Limit**.
2222

2323
:::note
@@ -42,23 +42,25 @@ To create the query size limit using **Advanced** configuration:
4242
It may take up to 5 minutes for a newly created budget to become active and enforceable in the system.
4343
:::
4444

45-
### View deatails about a Scan Budgets
45+
### View details about a Scan Budgets
4646

4747
To view the selected scan budget:
4848

4949
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Administration > Account > Usage Management**. <br/> [**New UI**](/docs/get-started/sumo-logic-ui/). In the top menu, select **Administration**, and then under **Account**, select **Usage Management**. You can also click the **Go To...** menu at the top of the screen and select **Usage Management**.
5050
1. Navigate to **Advanced** tab and click the row with the scan budget you want to view.
5151
1. In the details section: <br/><img src={useBaseUrl('/img/manage/account/view-scan-budget.png')} alt="view-scan-budget" style={{border:'1px solid gray'}} width="400"/>
52-
- **Edit**. Click the **Edit** button to open the pane for editing. Edit the query limit and click on **Save**.
52+
- **Edit**. Click the **Edit** button to open the pane for editing. Edit the required fields and click on **Save**.
5353
:::note
54-
You cannot edit the Scope, Action, and Details information.
54+
You can only edit the **Capacity** for *Org-wide Query Budget* set using Basic.
5555
:::
5656
- **Deactivate/Activate**. Click the **Deactivate/Activate** button to deactivate/activate the selected scan budget.
5757
- **Delete**. Click the **Delete** button to delete the selected scan budget.
5858
- **View violations**. Sumo Logic recommends a GB value per query as per the 95th percentile to be within the safe limits. You can also check the query size of the last 10 queries by clicking on **Click here** to help you determine the appropriate size limit.
59-
- **Budget Type**.
59+
- **Budget Type**. Defines the type of budget set: **Per Query Budget** or **Time-Based Budgets**(TBA).
60+
- **Per Query Budget**. Limits the data (in GBs) that a single query can consume.
61+
- **Time-Based Budgets**(TBA). Limits the data or credits consumed over a day, week, or month.
6062
- **Status**. Describes if the scan budget is active or inactive.
61-
- **Usage Category**.
63+
- **Usage Category**. Describes the type of scan. For Flex this is shown as Flex scan and for Data tier this is shown as Infrequent scan.
6264
- **Applied to Roles**. Describes the roles for which the selected scan budget is applied for.
6365
- **Excluded to Roles**. Describes the roles for which the selected scan budget is excluded for.
6466
- **Applied to Users**. Describes the users for which the selected scan budget is applied for.
@@ -67,5 +69,12 @@ To view the selected scan budget:
6769
- **Action**. Describes the type of action sected to notify when the budget limit is reached.
6870
- **Created**. The user who created the scan budget.
6971
- **Modified**. The user that most recently modified the scan budget.
70-
- **Audit Logs**.
71-
- **System Audit**.
72+
- **Audit Logs**. Records the budget defenition changes. Click on **View Details** to view the budget defenition changes.
73+
- **System Audit**. Records the breaches and budget enforcement. Click on **View Details** to view the list of breaches.
74+
75+
76+
## FAQ
77+
78+
### Handle overlapping budgets
79+
80+
When you configure multiple budgets for the same user, the scope with the largest capacity takes precedence. If there is still an overlap, the budget with the most restrictive action takes precedence. For example, if you are a part of multiple groups with different query size budgets, the one with the largest capacity will be applied.

0 commit comments

Comments
 (0)