Skip to content

Commit cc55203

Browse files
committed
Changing the applicable occurrences of the word 'blade' to 'pane' or 'section'
1 parent 9a2e1b9 commit cc55203

13 files changed

+48
-45
lines changed

articles/azure-monitor/agents/gateway.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -292,7 +292,7 @@ To configure specific servers or groups to use the Log Analytics gateway server:
292292

293293
1. Open the Operations Manager console and select the **Authoring** workspace.
294294
1. In the Authoring workspace, select **Rules**.
295-
1. On the Operations Manager toolbar, select the **Scope** button. If this button is not available, make sure you have selected an object, not a folder, in the **Monitoring** blade. The **Scope Management Pack Objects** dialog box displays a list of common targeted classes, groups, or objects.
295+
1. On the Operations Manager toolbar, select the **Scope** button. If this button is not available, make sure you have selected an object, not a folder, in the **Monitoring** pane. The **Scope Management Pack Objects** dialog box displays a list of common targeted classes, groups, or objects.
296296
1. In the **Look for** field, enter **Health Service** and select it from the list. Select **OK**.
297297
1. Search for **Advisor Proxy Setting Rule**.
298298
1. On the Operations Manager toolbar, select **Overrides** and then point to **Override the Rule\For a specific object of class: Health Service** and select an object from the list. Or create a custom group that contains the health service object of the servers you want to apply this override to. Then apply the override to your custom group.

articles/azure-monitor/app/api-custom-events-metrics.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ The core API is uniform across all platforms, apart from a few variations like `
2020

2121
| Method | Used for |
2222
| --- | --- |
23-
| [`TrackPageView`](#page-views) |Pages, screens, blades, or forms. |
23+
| [`TrackPageView`](#page-views) |Pages, screens, panes, or forms. |
2424
| [`TrackEvent`](#trackevent) |User actions and other events. Used to track user behavior or to monitor performance. |
2525
| [`GetMetric`](#getmetric) |Zero and multidimensional metrics, centrally configured aggregation, C# only. |
2626
| [`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
220220
221221
## Page views
222222

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.
224224

225225
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.
226226

articles/azure-monitor/app/javascript.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -204,7 +204,7 @@ Most configuration fields are named so that they can default to false. All field
204204
| disableFlush&#8203;OnBeforeUnload | If true, flush method won't be called when `onBeforeUnload` event triggers. | boolean<br/> false |
205205
| enableSessionStorageBuffer | If true, the buffer with all unsent telemetry is stored in session storage. The buffer is restored on page load. | boolean<br />true |
206206
| 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 |
208208
| 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 |
209209
| 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 |
210210
| 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 |

articles/azure-monitor/faq.yml

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -508,7 +508,10 @@ sections:
508508
How much does it cost?
509509
answer: |
510510
* 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.
512515
513516
- question: What do Application Insights modify in my project?
514517
answer: |
@@ -1014,7 +1017,7 @@ sections:
10141017
- question: |
10151018
Is there support for Kubernetes RBAC enabled AKS clusters?
10161019
answer: |
1017-
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.
1020+
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.
10181021
10191022
- question: |
10201023
How do I enable log collection for containers in the kube-system namespace through Helm?
@@ -1124,7 +1127,7 @@ sections:
11241127
answer: |
11251128
The VM insights Map feature is based on Service Map, but has the following differences:
11261129
1127-
* The Map view can be accessed from the VM blade and from VM insights under Azure Monitor.
1130+
* The Map view can be accessed from the VM pane and from VM insights under Azure Monitor.
11281131
* 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.
11291132
* There's a new API that is used to create the maps to better support more complex maps.
11301133
* 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.

articles/azure-monitor/insights/ad-assessment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ View the summarized compliance assessments for your infrastructure and then dril
108108

109109
1. On the **Overview** page, click the **Active Directory Health Check** tile.
110110

111-
2. On the **Health Check** page, review the summary information in one of the focus area blades 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.
112112

113113
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.
114114

articles/azure-monitor/insights/dns-analytics.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ From the Log Analytics workspace in the Azure portal, select **Workspace summary
5757

5858
You can modify the list to add any domain name suffix that you want to view lookup insights for. You can also remove any domain name suffix that you don't want to view lookup insights for.
5959

60-
- **Talkative Client Threshold**. DNS clients that exceed the threshold for the number of lookup requests are highlighted in the **DNS Clients** blade. The default threshold is 1,000. You can edit the threshold.
60+
- **Talkative Client Threshold**. DNS clients that exceed the threshold for the number of lookup requests are highlighted in the **DNS Clients** pane. The default threshold is 1,000. You can edit the threshold.
6161

6262
![Allowlisted domain names](./media/dns-analytics/dns-config.png)
6363

@@ -89,11 +89,11 @@ The solution dashboard shows summarized information for the various features of
8989

9090
![Time selection control](./media/dns-analytics/dns-time.png)
9191

92-
The solution dashboard shows the following blades:
92+
The solution dashboard shows the following sections:
9393

9494
**DNS Security**. Reports the DNS clients that are trying to communicate with malicious domains. By using Microsoft threat intelligence feeds, DNS Analytics can detect client IPs that are trying to access malicious domains. In many cases, malware-infected devices "dial out" to the "command and control" center of the malicious domain by resolving the malware domain name.
9595

96-
![DNS Security blade](./media/dns-analytics/dns-security-blade.png)
96+
![DNS Security section](./media/dns-analytics/dns-security-blade.png)
9797

9898
When you click a client IP in the list, Log Search opens and shows the lookup details of the respective query. In the following example, DNS Analytics detected that the communication was done with an [IRCbot](https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?Name=Backdoor:Win32/IRCbot&threatId=2621):
9999

@@ -111,11 +111,11 @@ The information helps you to identify the:
111111

112112
**Domains Queried**. Provides the most frequent domain names being queried by the DNS clients in your environment. You can view the list of all the domain names queried. You can also drill down into the lookup request details of a specific domain name in Log Search.
113113

114-
![Domains Queried blade](./media/dns-analytics/domains-queried-blade.png)
114+
![Domains Queried section](./media/dns-analytics/domains-queried-blade.png)
115115

116116
**DNS Clients**. Reports the clients *breaching the threshold* for number of queries in the chosen time period. You can view the list of all the DNS clients and the details of the queries made by them in Log Search.
117117

118-
![DNS Clients blade](./media/dns-analytics/dns-clients-blade.png)
118+
![DNS Clients section](./media/dns-analytics/dns-clients-blade.png)
119119

120120
**Dynamic DNS Registrations**. Reports name registration failures. All registration failures for address [resource records](https://en.wikipedia.org/wiki/List_of_DNS_record_types) (Type A and AAAA) are highlighted along with the client IPs that made the registration requests. You can then use this information to find the root cause of the registration failure by following these steps:
121121

@@ -127,11 +127,11 @@ The information helps you to identify the:
127127

128128
1. Check whether the zone is configured for secure dynamic update or not.
129129

130-
![Dynamic DNS Registrations blade](./media/dns-analytics/dynamic-dns-reg-blade.png)
130+
![Dynamic DNS Registrations section](./media/dns-analytics/dynamic-dns-reg-blade.png)
131131

132132
**Name registration requests**. The upper tile shows a trendline of successful and failed DNS dynamic update requests. The lower tile lists the top 10 clients that are sending failed DNS update requests to the DNS servers, sorted by the number of failures.
133133

134-
![Name registration requests blade](./media/dns-analytics/name-reg-req-blade.png)
134+
![Name registration requests section](./media/dns-analytics/name-reg-req-blade.png)
135135

136136
**Sample DDI Analytics Queries**. Contains a list of the most common search queries that fetch raw analytics data directly.
137137

articles/azure-monitor/insights/scom-assessment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -208,7 +208,7 @@ View the summarized compliance assessments for your infrastructure and then dril
208208
2. In the Azure portal, click **More services** found on the lower left-hand corner. In the list of resources, type **Log Analytics**. As you begin typing, the list filters based on your input. Select **Log Analytics**.
209209
3. In the Log Analytics subscriptions pane, select a workspace and then click the **Workspace summary** menu item.
210210
4. On the **Overview** page, click the **System Center Operations Manager Health Check** tile.
211-
5. On the **System Center Operations Manager Health Check** page, review the summary information in one of the focus area blades and then click one to view recommendations for that focus area.
211+
5. On the **System Center Operations Manager 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.
212212
6. 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.<br><br> ![focus area](./media/scom-assessment/log-analytics-scom-healthcheck-dashboard-02.png)<br>
213213
7. You can take corrective actions suggested in **Suggested Actions**. When the item has been addressed, later assessments will record that recommended actions were taken and your compliance score will increase. Corrected items appear as **Passed Objects**.
214214

articles/azure-monitor/insights/sql-assessment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ View the summarized compliance assessments for your infrastructure and then dril
155155
2. In the Azure portal, click **More services** found on the lower left-hand corner. In the list of resources, type **Monitor**. As you begin typing, the list filters based on your input. Select **Monitor**.
156156
3. In the **Insights** section of the menu, select **More**.
157157
4. On the **Overview** page, click the **SQL Health Check** tile.
158-
5. On the **Health Check** page, review the summary information in one of the focus area blades and then click one to view recommendations for that focus area.
158+
5. 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.
159159
6. 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.<br><br> ![image of SQL Health Check recommendations](./media/sql-assessment/sql-healthcheck-dashboard-02.png)<br>
160160
7. You can take corrective actions suggested in **Suggested Actions**. When the item has been addressed, later assessments will record that recommended actions were taken and your compliance score will increase. Corrected items appear as **Passed Objects**.
161161

articles/azure-monitor/insights/vmware.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ The VMware tile appears in your Log Analytics workspace. It provides a high-leve
104104
![Screenshot shows the VMware tile, displaying nine failures.](./media/vmware/tile.png)
105105
106106
#### Navigate the dashboard view
107-
In the **VMware** dashboard view, blades are organized by:
107+
In the **VMware** dashboard view, sections are organized by:
108108
109109
* Failure Status Count
110110
* Top Host by Event Counts
@@ -116,7 +116,7 @@ In the **VMware** dashboard view, blades are organized by:
116116
117117
![solution2](./media/vmware/solutionview1-2.png)
118118
119-
Click any blade to open Log Analytics search pane that shows detailed information specific for the blade.
119+
Click any section to open Log Analytics search pane that shows detailed information specific for the section.
120120
121121
From here, you can edit the log query to modify it for something specific. For details on creating log queries, see [Find data using log queries in Azure Monitor](../logs/log-query-overview.md).
122122
@@ -129,12 +129,12 @@ You can drill further by clicking an ESXi host or an event type.
129129
130130
When you click an ESXi host name, you view information from that ESXi host. If you want to narrow results with the event type, add `“ProcessName_s=EVENT TYPE”` in your search query. You can select **ProcessName** in the search filter. That narrows the information for you.
131131
132-
![Screenshot of the ESXi Host Per Event Count and Breakdown Per Event Type blades in the VMware Monitoring dashboard view.](./media/vmware/eventhostdrilldown.png)
132+
![Screenshot of the ESXi Host Per Event Count and Breakdown Per Event Type sections in the VMware Monitoring dashboard view.](./media/vmware/eventhostdrilldown.png)
133133
134134
#### Find high VM activities
135135
A virtual machine can be created and deleted on any ESXi host. It's helpful for an administrator to identify how many VMs an ESXi host creates. That in-turn, helps to understand performance and capacity planning. Keeping track of VM activity events is crucial when managing your environment.
136136
137-
![Screenshot of the Virtual Machine Activities blade in the VMware Monitoring dashboard, showing a graph of VM creation and deletion by the ESXi host.](./media/vmware/vmactivities1.png)
137+
![Screenshot of the Virtual Machine Activities section in the VMware Monitoring dashboard, showing a graph of VM creation and deletion by the ESXi host.](./media/vmware/vmactivities1.png)
138138
139139
If you want to see additional ESXi host VM creation data, click an ESXi host name.
140140

0 commit comments

Comments
 (0)