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-data-export.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,12 +29,12 @@ Log Analytics workspace data export continuously exports data from a Log Analyti
29
29
30
30
## Limitations
31
31
32
-
- Configuration can currently be performed using CLI or REST requests. Azure portal or PowerShell are not supported yet.
32
+
- Configuration currently can be performed using CLI or REST requests. Azure portal or PowerShell are not supported yet.
33
33
- The `--export-all-tables` option in CLI and REST isn't supported and will be removed. You should provide the list of tables in export rules explicitly.
34
-
- Supported tables are currently limited those specified in the [supported tables](#supported-tables) section below. For example, custom log tables aren't currently supported.
34
+
- Supported tables currently are limited those specified in the [supported tables](#supported-tables) section below. For example, custom log tables currently aren't supported.
35
35
- If the data export rule includes an unsupported table, the operation will succeed, but no data will be exported for that table until the table gets supported.
36
36
- If the data export rule includes a table that doesn't exist, it will fail with error `Table <tableName> does not exist in the workspace`.
37
-
- Data export will be available in all regions, but currently not available in the following: Azure Government regions, Japan West, Brazil south east, Norway East, Norway West, UAE North, UAE Central, Australia Central 2, Switzerland North, Switzerland West, Germany West Central, South India, France South, Japan West
37
+
- Data export will be available in all regions, but currently it's not available in the following: Azure Government regions, Japan West, Brazil south east, Norway East, Norway West, UAE North, UAE Central, Australia Central 2, Switzerland North, Switzerland West, Germany West Central, South India, France South, Japan West
38
38
- You can define up to 10 enabled rules in your workspace. Additional rules are allowed but in disable state.
39
39
- Destination must be unique across all export rules in your workspace.
40
40
- The destination storage account or event hub must be in the same region as the Log Analytics workspace.
@@ -44,7 +44,7 @@ Log Analytics workspace data export continuously exports data from a Log Analyti
44
44
Data export will continue to retry sending data for up to 30 minutes in the event that the destination is unavailable. If it's still unavailable after 30 minutes then data will be discarded until the destination becomes available.
45
45
46
46
## Cost
47
-
There are currently no additional charges for the data export feature. Pricing for data export will be announced in the future and a notice period provided prior to the start of billing. If you choose to continue using data export after the notice period, you will be billed at the applicable rate.
47
+
Currently, there are no additional charges for the data export feature. Pricing for data export will be announced in the future and a notice period provided prior to the start of billing. If you choose to continue using data export after the notice period, you will be billed at the applicable rate.
48
48
49
49
## Export destinations
50
50
@@ -66,11 +66,11 @@ Data is sent to your event hub in near-real-time as it reaches Azure Monitor. An
66
66
> The [number of supported event hubs per 'Basic' and 'Standard' namespaces tiers is 10](../../event-hubs/event-hubs-quotas.md#common-limits-for-all-tiers). If you export more than 10 tables, either split the tables between several export rules to different event hub namespaces, or provide event hub name in the export rule and export all tables to that event hub.
67
67
68
68
Considerations:
69
-
1. The 'Basic' event hub sku supports a lower event size [limit](../../event-hubs/event-hubs-quotas.md#basic-vs-standard-tiers) and some logs in your workspace can exceed it and be dropped. We recommend using a 'Standard' or 'Dedicated' event hub as an export destination.
69
+
1. The 'Basic' event hub SKU supports a lower event size [limit](../../event-hubs/event-hubs-quotas.md#basic-vs-standard-tiers) and some logs in your workspace can exceed it and be dropped. We recommend using a 'Standard' or 'Dedicated' event hub as an export destination.
70
70
2. The volume of exported data often increases over time, and the event hub scale needs to be increased to handle larger transfer rates and avoid throttling scenarios and data latency. You should use the auto-inflate feature of Event Hubs to automatically scale up and increase the number of throughput units to meet usage needs. See [Automatically scale up Azure Event Hubs throughput units](../../event-hubs/event-hubs-auto-inflate.md) for details.
71
71
72
72
## Prerequisites
73
-
The following prerequisites must be completed before configuring Log Analytics data export.
73
+
The following prerequisites must be completed before configuring Log Analytics data export:
74
74
75
75
- Destinations must be created prior to the export rule configuration and should be in the same region as your Log Analytics workspace. If you need to replicate your data to other storage accounts, you can use any of the [Azure Storage redundancy options](../../storage/common/storage-redundancy.md).
76
76
- The storage account must be StorageV1 or StorageV2. Classic storage is not supported
@@ -539,7 +539,7 @@ If the data export rule includes a table that doesn't exist, it will fail with t
539
539
540
540
541
541
## Supported tables
542
-
Supported tables are currently limited to those specified below. All data from the table will be exported unless limitations are specified. This list will be updated as support for additional tables is added.
542
+
Supported tables currently are limited to those specified below. All data from the table will be exported unless limitations are specified. This list will be updated as support for additional tables is added.
543
543
544
544
545
545
| Table | Limitations |
@@ -639,7 +639,7 @@ Supported tables are currently limited to those specified below. All data from t
639
639
| NWConnectionMonitorTestResult ||
640
640
| OfficeActivity | Partial support – some of the data to ingested via webhooks from O365 into LA. This portion is missing in export currently. |
641
641
| Operation | Partial support – some of the data is ingested through internal services that isn't supported for export. This portion is missing in export currently. |
642
-
| Perf | Partial support – only windows perf data is currently supported. The Linux perf data is missing in export currently. |
642
+
| Perf | Partial support – only Windows perf data currently is supported. The Linux perf data is missing in export currently. |
0 commit comments