Skip to content

Commit f285c6e

Browse files
committed
Merge branch '2022-02-22-add-shir-monitoring-docs' of https://github.com/jonburchel/azure-docs-pr-jburcheledits into 2022-02-22-add-shir-monitoring-docs
2 parents 2f60374 + 746bb2b commit f285c6e

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/data-factory/how-to-configure-shir-for-log-analytics-collection.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,10 @@ The event journal name we must configure are:
5252
5353
### Select Performance counters
5454

55-
In the same configuration pane, you can select on **Windows Performance Counters** to select individual performance counters to send up to log analytics. Keep in mind that performance counters are, by their nature, a continuous data stream. Therefore, it’s crucial that you consider the impact of data collection on the total cost of your Azure Monitor/Log Analytics deployment. Unless an allowed data ingestion budget has been granted and a constant ingestion of data has been allowed and budgeted for, gathering performance counters should only be configured for a defined period to establish a performance baseline.
55+
In the same configuration pane, you can click on **Windows Performance Counters** to select individual performance counters to send up to log analytics.
56+
57+
> [!IMPORTANT]
58+
> Keep in mind that performance counters are, by their nature, a continuous data stream. Therefore, it’s crucial that you consider the impact of data collection on the total cost of your Azure Monitor/Log Analytics deployment. Unless an allowed data ingestion budget has been granted and a constant ingestion of data has been allowed and budgeted for, gathering performance counters should only be configured for a defined period to establish a performance baseline.
5659
5760
In the interface, when first configuring it, a suggested counter set will be recommended. Select those that apply to the type of performance analysis you want to perform. **%CPU** and **Available memory** are commonly monitored counters but others like **Network bandwidth consumption** can be useful in scenarios where the data volume is large, and bandwidth or execution time are constrained.
5861

0 commit comments

Comments
 (0)