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/agents/data-collection-text-log.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,15 +85,15 @@ A [data collection endpoint (DCE)](../essentials/data-collection-endpoint-overvi
85
85
86
86
1. In the Azure portal's search box, type in *template* and then select **Deploy a custom template**.
87
87
88
-
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/deploy-custom-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/deploy-custom-template.png" alt-text="Screenshot that shows portal blade to deploy custom template.":::
88
+
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/deploy-custom-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/deploy-custom-template.png" alt-text="Screenshot that shows the Azure portal with template entered in the search box and Deploy a custom template highlighted in the search results.":::
89
89
90
90
2. Click **Build your own template in the editor**.
91
91
92
-
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/build-custom-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/build-custom-template.png" alt-text="Screenshot that shows portal blade to build template in the editor.":::
92
+
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/build-custom-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/build-custom-template.png" alt-text="Screenshot that shows portal screen to build template in the editor.":::
93
93
94
94
3. Paste the Resource Manager template below into the editor and then click **Save**. You don't need to modify this template since you will provide values for its parameters.
95
95
96
-
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/edit-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/edit-template.png" alt-text="Screenshot that shows portal blade to edit Resource Manager template.":::
96
+
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/edit-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/edit-template.png" alt-text="Screenshot that shows portal screen to edit Resource Manager template.":::
97
97
98
98
```json
99
99
{
@@ -138,13 +138,13 @@ A [data collection endpoint (DCE)](../essentials/data-collection-endpoint-overvi
138
138
139
139
4. On the **Custom deployment** screen, specify a **Subscription** and **Resource group** to store the data collection rule and then provide values a **Name** for the data collection endpoint. The **Location** should be the same location as the workspace. The **Region** will already be populated and is used for the location of the data collection endpoint.
140
140
141
-
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/custom-deployment-values.png" lightbox="../logs/media/tutorial-workspace-transformations-api/custom-deployment-values.png" alt-text="Screenshot that shows portal blade to edit custom deployment values for data collection endpoint.":::
141
+
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/custom-deployment-values.png" lightbox="../logs/media/tutorial-workspace-transformations-api/custom-deployment-values.png" alt-text="Screenshot that shows portal screen to edit custom deployment values for data collection endpoint.":::
142
142
143
143
5. Click **Review + create** and then **Create** when you review the details.
144
144
145
145
6. Once the DCE is created, select it so you can view its properties. Note the **Logs ingestion URI** since you'll need this in a later step.
146
146
147
-
:::image type="content" source="../logs/media/tutorial-logs-ingestion-api/data-collection-endpoint-overview.png" lightbox="../logs/media/tutorial-logs-ingestion-api/data-collection-endpoint-overview.png" alt-text="Screenshot that shows portal blade with details of data collection endpoint uri.":::
147
+
:::image type="content" source="../logs/media/tutorial-logs-ingestion-api/data-collection-endpoint-overview.png" lightbox="../logs/media/tutorial-logs-ingestion-api/data-collection-endpoint-overview.png" alt-text="Screenshot that shows the DCE Overview pane in the portal with details of data collection endpoint uri.":::
148
148
149
149
7. Click **JSON View** to view other details for the DCE. Copy the **Resource ID** since you'll need this in a later step.
150
150
@@ -160,11 +160,11 @@ The [data collection rule (DCR)](../essentials/data-collection-rule-overview.md)
160
160
161
161
1. In the Azure portal's search box, type in *template* and then select **Deploy a custom template**.
162
162
163
-
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/deploy-custom-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/deploy-custom-template.png" alt-text="Screenshot that shows portal blade to deploy custom template.":::
163
+
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/deploy-custom-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/deploy-custom-template.png" alt-text="Screenshot that shows the Azure portal with template entered in the search box and Deploy a custom template highlighted in the search results.":::
164
164
165
165
2. Click **Build your own template in the editor**.
166
166
167
-
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/build-custom-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/build-custom-template.png" alt-text="Screenshot that shows portal blade to build template in the editor.":::
167
+
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/build-custom-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/build-custom-template.png" alt-text="Screenshot that shows portal screen to build template in the editor.":::
168
168
169
169
3. Paste one of the Resource Manager templates below into the editor and then change the following values:
170
170
@@ -175,7 +175,7 @@ The [data collection rule (DCR)](../essentials/data-collection-rule-overview.md)
175
175
176
176
4. Click **Save**.
177
177
178
-
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/edit-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/edit-template.png" alt-text="Screenshot that shows portal blade to edit Resource Manager template.":::
178
+
:::image type="content" source="../logs/media/tutorial-workspace-transformations-api/edit-template.png" lightbox="../logs/media/tutorial-workspace-transformations-api/edit-template.png" alt-text="Screenshot that shows portal screen to edit Resource Manager template.":::
179
179
180
180
**Data collection rule for text log**
181
181
@@ -400,13 +400,13 @@ The [data collection rule (DCR)](../essentials/data-collection-rule-overview.md)
400
400
401
401
5. On the **Custom deployment** screen, specify a **Subscription** and **Resource group** to store the data collection rule and then provide values defined in the template. This includes a **Name** for the data collection rule and the **Workspace Resource ID** and **Endpoint Resource ID**. The **Location** should be the same location as the workspace. The **Region** will already be populated and is used for the location of the data collection rule.
402
402
403
-
:::image type="content" source="media/data-collection-text-log/custom-deployment-values.png" lightbox="media/data-collection-text-log/custom-deployment-values.png" alt-text="Screenshot that shows portal blade to edit custom deployment values for data collection rule.":::
403
+
:::image type="content" source="media/data-collection-text-log/custom-deployment-values.png" lightbox="media/data-collection-text-log/custom-deployment-values.png" alt-text="Screenshot that shows the Custom Deployment screen in the portal to edit custom deployment values for data collection rule.":::
404
404
405
405
6. Click **Review + create** and then **Create** when you review the details.
406
406
407
407
7. When the deployment is complete, expand the **Deployment details** box and click on your data collection rule to view its details. Click **JSON View**.
408
408
409
-
:::image type="content" source="media/data-collection-text-log/data-collection-rule-details.png" lightbox="media/data-collection-text-log/data-collection-rule-details.png" alt-text="Screenshot that shows portal blade with data collection rule details.":::
409
+
:::image type="content" source="media/data-collection-text-log/data-collection-rule-details.png" lightbox="media/data-collection-text-log/data-collection-rule-details.png" alt-text="Screenshot that shows the Overview pane in the portal with data collection rule details.":::
410
410
411
411
8. Change the API version to **2021-09-01-preview**.
412
412
@@ -419,15 +419,15 @@ The final step is to create a data collection association that associates the da
419
419
420
420
1. From the **Monitor** menu in the Azure portal, select **Data Collection Rules** and select the rule that you just created.
421
421
422
-
:::image type="content" source="media/data-collection-text-log/data-collection-rules.png" lightbox="media/data-collection-text-log/data-collection-rules.png" alt-text="Screenshot that shows portal blade with data collection rules menu item.":::
422
+
:::image type="content" source="media/data-collection-text-log/data-collection-rules.png" lightbox="media/data-collection-text-log/data-collection-rules.png" alt-text="Screenshot that shows the Data Collection Rules pane in the portal with data collection rules menu item.":::
423
423
424
424
2. Select **Resources** and then click **Add** to view the available resources.
425
425
426
-
:::image type="content" source="media/data-collection-text-log/data-collection-rules.png" lightbox="media/data-collection-text-log/data-collection-rules.png" alt-text="Screenshot that shows portal blade with resources for the data collection rule.":::
426
+
:::image type="content" source="media/data-collection-text-log/data-collection-rules.png" lightbox="media/data-collection-text-log/data-collection-rules.png" alt-text="Screenshot that shows the Data Collection Rules pane in the portal with resources for the data collection rule.":::
427
427
428
428
3. Select either individual agents to associate the data collection rule, or select a resource group to create an association for all agents in that resource group. Click **Apply**.
429
429
430
-
:::image type="content" source="media/data-collection-text-log/select-resources.png" lightbox="media/data-collection-text-log/select-resources.png" alt-text="Screenshot that shows portal blade to add resources to the data collection rule.":::
430
+
:::image type="content" source="media/data-collection-text-log/select-resources.png" lightbox="media/data-collection-text-log/select-resources.png" alt-text="Screenshot that shows the Resources pane in the portal to add resources to the data collection rule.":::
431
431
432
432
## Troubleshooting - text logs
433
433
Use the following steps to troubleshoot collection of text logs.
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/api-custom-events-metrics.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ The core API is uniform across all platforms, apart from a few variations like `
20
20
21
21
| Method | Used for |
22
22
| --- | --- |
23
-
|[`TrackPageView`](#page-views)|Pages, screens, blades, or forms. |
23
+
|[`TrackPageView`](#page-views)|Pages, screens, panes, or forms. |
24
24
|[`TrackEvent`](#trackevent)|User actions and other events. Used to track user behavior or to monitor performance. |
25
25
|[`GetMetric`](#getmetric)|Zero and multidimensional metrics, centrally configured aggregation, C# only. |
26
26
|[`TrackMetric`](#trackmetric)|Performance measurements such as queue lengths not related to specific events. |
@@ -220,7 +220,7 @@ The telemetry is available in the `customMetrics` table in [Application Insights
220
220
221
221
## Page views
222
222
223
-
In a device or webpage app, page view telemetry is sent by default when each screen or page is loaded. But you can change the default to track page views at more or different times. For example, in an app that displays tabs or blades, you might want to track a page whenever the user opens a new blade.
223
+
In a device or webpage app, page view telemetry is sent by default when each screen or page is loaded. But you can change the default to track page views at more or different times. For example, in an app that displays tabs or panes, you might want to track a page whenever the user opens a new pane.
224
224
225
225
User and session data is sent as properties along with page views, so the user and session charts come alive when there's page view telemetry.
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/javascript.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -204,7 +204,7 @@ Most configuration fields are named so that they can default to false. All field
204
204
| disableFlush​OnBeforeUnload | If true, flush method won't be called when `onBeforeUnload` event triggers. | boolean<br/> false |
205
205
| enableSessionStorageBuffer | If true, the buffer with all unsent telemetry is stored in session storage. The buffer is restored on page load. | boolean<br />true |
206
206
| cookieCfg | Defaults to cookie usage enabled. For full defaults, see [ICookieCfgConfig](#icookiemgrconfig) settings. |[ICookieCfgConfig](#icookiemgrconfig)<br>(Since 2.6.0)<br/>undefined |
207
-
|~~isCookieUseDisabled~~<br>disableCookiesUsage | If true, the SDK won't store or read any data from cookies. Disables the User and Session cookies and renders the usage blades and experiences useless. `isCookieUseDisable` is deprecated in favor of `disableCookiesUsage`. When both are provided, `disableCookiesUsage` takes precedence.<br>(Since v2.6.0) And if `cookieCfg.enabled` is also defined, it will take precedence over these values. Cookie usage can be re-enabled after initialization via `core.getCookieMgr().setEnabled(true)`. | Alias for [`cookieCfg.enabled`](#icookiemgrconfig)<br>false |
207
+
|~~isCookieUseDisabled~~<br>disableCookiesUsage | If true, the SDK won't store or read any data from cookies. Disables the User and Session cookies and renders the usage panes and experiences useless. `isCookieUseDisable` is deprecated in favor of `disableCookiesUsage`. When both are provided, `disableCookiesUsage` takes precedence.<br>(Since v2.6.0) And if `cookieCfg.enabled` is also defined, it will take precedence over these values. Cookie usage can be re-enabled after initialization via `core.getCookieMgr().setEnabled(true)`. | Alias for [`cookieCfg.enabled`](#icookiemgrconfig)<br>false |
208
208
| cookieDomain | Custom cookie domain. This option is helpful if you want to share Application Insights cookies across subdomains.<br>(Since v2.6.0) If `cookieCfg.domain` is defined, it will take precedence over this value. | Alias for [`cookieCfg.domain`](#icookiemgrconfig)<br>null |
209
209
| cookiePath | Custom cookie path. This option is helpful if you want to share Application Insights cookies behind an application gateway.<br>If `cookieCfg.path` is defined, it will take precedence over this value. | Alias for [`cookieCfg.path`](#icookiemgrconfig)<br>(Since 2.6.0)<br/>null |
210
210
| isRetryDisabled | If false, retry on 206 (partial success), 408 (timeout), 429 (too many requests), 500 (internal server error), 503 (service unavailable), and 0 (offline, only if detected). | boolean<br/>false |
Copy file name to clipboardExpand all lines: articles/azure-monitor/faq.yml
+6-3Lines changed: 6 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -508,7 +508,10 @@ sections:
508
508
How much does it cost?
509
509
answer: |
510
510
* Open the **Usage and estimated costs page** in an Application Insights resource. There's a chart of recent usage. You can set a data volume cap, if you want.
511
-
* Open the [Azure Billing blade](https://portal.azure.com/#blade/Microsoft_Azure_Billing/BillingBlade/Overview) to see your bills across all resources.
511
+
* To see your bills across all resources:
512
+
1. Open the [Azure portal](https://portal.azure.com)
513
+
1. Search for "Cost Management" and use the Cost analysis pane to see forecasted costs.
514
+
1. Search for "Cost Management and Billing" and open the Billing scopes pane to see current charges across subscriptions.
512
515
513
516
- question: What do Application Insights modify in my project?
514
517
answer: |
@@ -1048,7 +1051,7 @@ sections:
1048
1051
- question: |
1049
1052
Is there support for Kubernetes RBAC enabled AKS clusters?
1050
1053
answer: |
1051
-
The Container Monitoring solution doesn't support Kubernetes RBAC, but it's supported with Container insights. The solution details page may not show the right information in the blades that show data for these clusters.
1054
+
The Container Monitoring solution doesn't support Kubernetes RBAC, but it's supported with Container insights. The solution details page may not show the right information in the panes that show data for these clusters.
1052
1055
1053
1056
- question: |
1054
1057
How do I enable log collection for containers in the kube-system namespace through Helm?
@@ -1158,7 +1161,7 @@ sections:
1158
1161
answer: |
1159
1162
The VM insights Map feature is based on Service Map, but has the following differences:
1160
1163
1161
-
* The Map view can be accessed from the VM blade and from VM insights under Azure Monitor.
1164
+
* The Map view can be accessed from the VM pane and from VM insights under Azure Monitor.
1162
1165
* The connections in the Map are now clickable and display a view of the connection metric data in the side panel for the selected connection.
1163
1166
* There's a new API that is used to create the maps to better support more complex maps.
1164
1167
* Monitored VMs are now included in the client group node, and the donut chart shows the proportion of monitored vs unmonitored virtual machines in the group. It can also be used to filter the list of machines when the group is expanded.
Copy file name to clipboardExpand all lines: articles/azure-monitor/insights/ad-assessment.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ View the summarized compliance assessments for your infrastructure and then dril
108
108
109
109
1. On the **Overview** page, click the **Active Directory Health Check** tile.
110
110
111
-
2. On the **Health Check** page, review the summary information in one of the focus area panes and then click one to view recommendations for that focus area.
111
+
2. On the **Health Check** page, review the summary information in one of the focus area sections and then click one to view recommendations for that focus area.
112
112
113
113
3. On any of the focus area pages, you can view the prioritized recommendations made for your environment. Click a recommendation under **Affected Objects** to view details about why the recommendation is made.
Copy file name to clipboardExpand all lines: articles/azure-monitor/insights/capacity-performance.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,9 +96,9 @@ Click on the Capacity and Performance tile to open the Capacity and Performance
96
96
-**Host Density** The top tile shows the total number of hosts and virtual machines available to the solution. Click the top tile to view additional details in log search. Also lists all hosts and the number of virtual machines that are hosted. Click a host to drill into the VM results in a log search.
0 commit comments