You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/logs/logs-table-plans.md
+48-39Lines changed: 48 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,10 @@ ms.date: 07/04/2024
14
14
15
15
You can use one Log Analytics workspace to store any type of log required for any purpose. For example:
16
16
17
-
- High-volume, verbose data that requires **cheap long-term storage for audit and compliance**
18
-
- App and resource data for **troubleshooting** by developers
19
-
- Key event and performance data for scaling and alerting to ensure ongoing **operational excellence and security**
20
-
- Aggregated long-term data trends for **advanced analytics and machine learning**
17
+
* High-volume, verbose data that requires **cheap long-term storage for audit and compliance**
18
+
* App and resource data for **troubleshooting** by developers
19
+
* Key event and performance data for scaling and alerting to ensure ongoing **operational excellence and security**
20
+
* Aggregated long-term data trends for **advanced analytics and machine learning**
21
21
22
22
Table plans let you manage data costs based on how often you use the data in a table and the type of analysis you need the data for. This article explains and how to set a table's plan.
23
23
@@ -39,8 +39,9 @@ All tables support the Analytics plan and all DCR-based custom tables and [some
39
39
When you change a table's plan from Analytics to Basic, Azure monitor treats any data that's older than 30 days as long-term retention data based on the total retention period set for the table. In other words, the total retention period of the table remains unchanged, unless you explicitly [modify the long-term retention period](../logs/data-retention-configure.md).
40
40
41
41
> [!NOTE]
42
-
> You can switch a table's plan once a week.
43
-
# [Portal](#tab/portal-1)
42
+
> You can switch a table's plan once a week.
43
+
44
+
### [Portal](#tab/portal-1)
44
45
45
46
Analytics is the default table plan of all tables you create in the portal. You can switch between the Analytics and Basic plans, as described in this section.
46
47
@@ -62,7 +63,7 @@ To switch a table's plan in the Azure portal:
62
63
63
64
1. Select **Save**.
64
65
65
-
# [API](#tab/api-1)
66
+
###[API](#tab/api-1)
66
67
67
68
To configure a table for Basic logs or Analytics logs, call the [Tables - Update API](/rest/api/loganalytics/tables/create-or-update):
68
69
@@ -87,29 +88,29 @@ Container Insights uses `ContainerLog` by default. To switch to using `Container
Use this request body to change to Analytics Logs:
105
-
106
-
```http
107
-
{
108
-
"properties": {
109
-
"plan": "Analytics"
103
+
```
104
+
105
+
Use this request body to change to Analytics Logs:
106
+
107
+
```http
108
+
{
109
+
"properties": {
110
+
"plan": "Analytics"
111
+
}
110
112
}
111
-
}
112
-
```
113
+
```
113
114
114
115
**Sample response**
115
116
@@ -132,42 +133,50 @@ Status code: 200
132
133
}
133
134
```
134
135
135
-
# [CLI](#tab/cli-1)
136
+
###[CLI](#tab/cli-1)
136
137
137
138
To configure a table for Basic logs or Analytics logs, run the [az monitor log-analytics workspace table update](/cli/azure/monitor/log-analytics/workspace/table#az-monitor-log-analytics-workspace-table-update) command and set the `--plan` parameter to `Basic` or `Analytics`.
To configure a table's plan, use the [Update-AzOperationalInsightsTable](/powershell/module/az.operationalinsights/Update-AzOperationalInsightsTable) cmdlet:
0 commit comments