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
## <aname="using-dynamic-groups"></a>Using dynamic groups (preview)
562
+
## <aname="using-dynamic-groups"></a>Using dynamic groups
563
563
564
564
Update Management provides the ability to target a dynamic group of Azure VMs for update deployments. These groups are defined by a query, when an update deployment begins, the members of that group are evaluated. Dynamic groups do not work with classic VMs. When defining your query, the following items can be used together to populate the dynamic group
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-bindings-event-iot.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
@@ -16,7 +16,7 @@ ms.author: cshoe
16
16
---
17
17
# Azure IoT Hub bindings for Azure Functions
18
18
19
-
This article explains how to work with Azure Functions bindings for IoT Hub. The IoT Hub support is based on the [Azure Event Hubs Binding](link to event hub doc).
19
+
This article explains how to work with Azure Functions bindings for IoT Hub. The IoT Hub support is based on the [Azure Event Hubs Binding](functions-bindings-event-hubs.md).
Copy file name to clipboardExpand all lines: articles/azure-monitor/insights/ad-replication-status.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
@@ -39,7 +39,7 @@ If you don't want to connect any of your domain controllers directly to Azure Mo
39
39
3. On that computer, set the following registry key:<br>Key: **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Groups\<ManagementGroupName>\Solutions\ADReplication**<br>Value: **IsTarget**<br>Value Data: **true**
40
40
41
41
> [!NOTE]
42
-
> These changes do not take effect until your restart the Microsoft Monitoring Agent service (HealthService.exe).
42
+
> These changes do not take effect until you restart the Microsoft Monitoring Agent service (HealthService.exe).
43
43
> ### Install solution
44
44
> Follow the process described in [Install a monitoring solution](solutions.md#install-a-monitoring-solution) to add the **Active Directory Replication Status** solution to your Log Analytics workspace. There is no further configuration required.
Copy file name to clipboardExpand all lines: articles/azure-monitor/insights/container-insights-analyze.md
+33-6Lines changed: 33 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.service: azure-monitor
11
11
ms.topic: article
12
12
ms.tgt_pltfrm: na
13
13
ms.workload: infrastructure-services
14
-
ms.date: 02/08/2019
14
+
ms.date: 04/09/2019
15
15
ms.author: magoedte
16
16
---
17
17
@@ -95,7 +95,34 @@ The performance chart displays four performance metrics:
95
95
96
96
You can use the left/right arrow keys to cycle through each data point on the chart and the up/down arrow keys to cycle through the percentile lines.
97
97
98
-
When you switch to **Nodes**, **Controllers**, and **Containers** tab, automatically displayed on the right-side of the page is the property pane. It shows the properties of the item selected, including labels you define to organize Kubernetes objects. Click on the **>>** link in the pane to view\hide the pane.
98
+
Azure Monitor for containers also supports Azure Monitor [metrics explorer](../platform/metrics-getting-started.md), where you can create your own plot charts, correlate and investigate trends, and pin to dashboards. From metrics explorer, you can also use the criteria you have set to visualize your metrics as the basis of a [metric based alert rule](../platform/alerts-metric.md).
99
+
100
+
## View container metrics in metrics explorer
101
+
In metrics explorer, you can view aggregated node and pod utilization metrics from Azure Monitor for containers. The following table summarizes the details to help you understand how to use the metric charts to visualize container metrics.
102
+
103
+
|Namespace | Metric |
104
+
|----------|--------|
105
+
| insights.container/nodes ||
106
+
|| cpuUsageMillicores |
107
+
|| cpuUsagePercentage |
108
+
|| memoryRssBytes |
109
+
|| memoryRssPercentage |
110
+
|| memoryWorkingSetBytes |
111
+
|| memoryWorkingSetPercentage |
112
+
|| nodesCount |
113
+
| insights.container/pods ||
114
+
|| PodCount |
115
+
116
+
You can apply [splitting](../platform/metrics-charts.md#apply-splitting-to-a-chart) of a metric to view it by dimension and visualize how different segments of it compare to each other. For a node, you can segment the chart by the *host* dimension, and from a pod you can segment it by the following dimensions:
117
+
118
+
* Controller
119
+
* Kubernetes namespace
120
+
* Node
121
+
* Phase
122
+
123
+
## Analyze nodes, controllers, and container health
124
+
125
+
When you switch to **Nodes**, **Controllers**, and **Containers** tab, automatically displayed on the right-side of the page is the property pane. It shows the properties of the item-selected, including labels you define to organize Kubernetes objects. Click on the **>>** link in the pane to view\hide the pane.
@@ -128,7 +155,7 @@ By default, Performance data is based on the last six hours, but you can change
128
155
129
156
When you mouse over the bar graph under the **Trend** column, each bar shows either CPU or memory usage, depending on which metric is selected, within a sample period of 15 minutes. After you select the trend chart through a keyboard, you can use the Alt+PageUp or Alt+PageDown keys to cycle through each bar individually and get the same details as you would on mouseover.
130
157
131
-
158
+
132
159
133
160
In the next example, note for the first in the list - node *aks-nodepool1-*, the value for **Containers** is 9, which is a rollup of the total number of containers deployed.
134
161
@@ -171,10 +198,10 @@ The information that's displayed when you view controllers is described in the f
171
198
|--------|-------------|
172
199
| Name | The name of the controller.|
173
200
| Status | The rollup status of the containers when it has completed running with status, such as *OK*, *Terminated*, *Failed**Stopped*, or *Paused*. If the container is running, but the status was either not properly displayed or was not picked up by the agent and has not responded more than 30 minutes, the status is *Unknown*. Additional details of the status icon are provided in the table below.|
174
-
| Avg %, Min %, Max %, 50th %, 90th % |Rollup average of the average percentage of each entity for the selected metric and percentile. |
175
-
| Avg, Min, Max, 50th, 90th |Rollup of the average CPU millicore or memory performance of the container for the selected percentile. The average value is measured from the CPU/Memory limit set for a pod. |
201
+
| Avg %, Min %, Max %, 50th %, 90th % |Roll up average of the average percentage of each entity for the selected metric and percentile. |
202
+
| Avg, Min, Max, 50th, 90th |Roll up of the average CPU millicore or memory performance of the container for the selected percentile. The average value is measured from the CPU/Memory limit set for a pod. |
176
203
| Containers | Total number of containers for the controller or pod. |
177
-
| Restarts |Rollup of the restart count from containers. |
204
+
| Restarts |Roll up of the restart count from containers. |
178
205
| Uptime | Represents the time since a container started. |
179
206
| Node | Only for containers and pods. It shows which controller it is residing. |
180
207
| Trend Avg %, Min %, Max %, 50th %, 90th %| Bar graph trend represents the average percentile metric of the controller. |
Copy file name to clipboardExpand all lines: articles/azure-monitor/insights/solution-agenthealth.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,21 +70,21 @@ A record with a type of **Heartbeat** is created. These records have the proper
70
70
71
71
| Property | Description |
72
72
| --- | --- |
73
-
| Type |*Heartbeat*|
74
-
| Category | Value is *Direct Agent*, *SCOM Agent*, or *SCOM Management Server*.|
75
-
| Computer | Computer name.|
76
-
| OSType | Windows or Linux operating system.|
77
-
| OSMajorVersion | Operating system major version.|
78
-
| OSMinorVersion | Operating system minor version.|
79
-
| Version | Log Analytics Agent or Operations Manager Agent version.|
80
-
| SCAgentChannel | Value is *Direct* and/or *SCManagementServer*.|
81
-
| IsGatewayInstalled | If Log Analytics gateway is installed, value is *true*, otherwise value is *false*.|
82
-
| ComputerIP | IP address of the computer.|
83
-
| RemoteIPCountry | Geographic location where computer is deployed.|
84
-
| ManagementGroupName | Name of Operations Manager management group.|
85
-
| SourceComputerId | Unique ID of computer.|
86
-
| RemoteIPLongitude | Longitude of computer's geographic location.|
87
-
| RemoteIPLatitude | Latitude of computer's geographic location.|
73
+
|`Type`|*Heartbeat*|
74
+
|`Category`| Value is *Direct Agent*, *SCOM Agent*, or *SCOM Management Server*.|
75
+
|`Computer`| Computer name.|
76
+
|`OSType`| Windows or Linux operating system.|
77
+
|`OSMajorVersion`| Operating system major version.|
78
+
|`OSMinorVersion`| Operating system minor version.|
79
+
|`Version`| Log Analytics Agent or Operations Manager Agent version.|
80
+
|`SCAgentChannel`| Value is *Direct* and/or *SCManagementServer*.|
81
+
|`IsGatewayInstalled`| If Log Analytics gateway is installed, value is *true*, otherwise value is *false*.|
82
+
|`ComputerIP`| IP address of the computer.|
83
+
|`RemoteIPCountry`| Geographic location where computer is deployed.|
84
+
|`ManagementGroupName`| Name of Operations Manager management group.|
85
+
|`SourceComputerId`| Unique ID of computer.|
86
+
|`RemoteIPLongitude`| Longitude of computer's geographic location.|
87
+
|`RemoteIPLatitude`| Latitude of computer's geographic location.|
88
88
89
89
Each agent reporting to an Operations Manager management server will send two heartbeats, and SCAgentChannel property's value will include both **Direct** and **SCManagementServer** depending on what data sources and monitoring solutions you have enabled in your subscription. If you recall, data from solutions are either sent directly from an Operations Manager management server to Azure Monitor, or because of the volume of data collected on the agent, are sent directly from the agent to Azure Monitor. For heartbeat events which have the value **SCManagementServer**, the ComputerIP value is the IP address of the management server since the data is actually uploaded by it. For heartbeats where SCAgentChannel is set to **Direct**, it is the public IP address of the agent.
0 commit comments