master
yaml 10,412 lines 478 KB
Raw
1 plugin_name: go.d.plugin
2 modules:
3 - &module
4 meta: &meta
5 id: collector-go.d.plugin-azure_monitor
6 plugin_name: go.d.plugin
7 module_name: azure_monitor
8 monitored_instance:
9 name: Azure Monitor
10 link: https://learn.microsoft.com/azure/azure-monitor/
11 icon_filename: azure.svg
12 categories:
13 - data-collection.cloud-and-devops
14 keywords:
15 - azure
16 - monitor
17 - cloud
18 related_resources:
19 integrations:
20 list: []
21 info_provided_to_referring_integrations:
22 description: ""
23 overview: &overview
24 data_collection:
25 metrics_description: |
26 This collector provides real-time visibility into your Azure infrastructure by collecting platform metrics from the Azure Monitor Metrics API.
27
28 **Key capabilities:**
29
30 - **Multi-subscription** -- monitor resources across one or more Azure subscriptions in a single job
31 - **Automatic service detection** -- discovers resources and enables matching metric profiles without manual configuration
32 - **[38 built-in service profiles](https://github.com/netdata/netdata/tree/master/src/go/plugin/go.d/config/go.d/azure_monitor.profiles/default)** -- covers databases, compute, networking, storage, AI, analytics, and more
33 - **Flexible discovery** -- use structured filters (resource groups, regions, tags) or a custom Azure Resource Graph KQL query
34 method_description: &method_description |
35 It uses the [Azure Monitor Metrics batch API](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/migrate-to-batch-api) to collect metrics, grouping requests by subscription, region, and time grain. Resources are discovered via [Azure Resource Graph](https://learn.microsoft.com/en-us/azure/governance/resource-graph/overview) queries at startup and refreshed periodically. Authentication is handled through [Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/identity/) (service principal, managed identity, or default credentials).
36 supported_platforms:
37 include: []
38 exclude: []
39 multi_instance: true
40 additional_permissions:
41 description: |
42 The service principal or managed identity requires these Azure RBAC roles:
43
44 | Role | Purpose | Scope |
45 |:-----|:--------|:------|
46 | **Monitoring Reader** | Read Azure Monitor metrics | Subscription or resource group |
47 | **Reader** | Query Azure Resource Graph for resource discovery | Subscription or resource group |
48 default_behavior:
49 auto_detection:
50 description: |
51 The collector has two discovery phases:
52
53 **Bootstrap (first run)**
54
55 - With the default `profiles.mode: auto`, the collector queries Azure Resource Graph within the configured `subscription_ids` to find candidate resources.
56 - It matches discovered resource types against [built-in profiles](https://github.com/netdata/netdata/tree/master/src/go/plugin/go.d/config/go.d/azure_monitor.profiles/default) and automatically enables the relevant ones.
57 - Discovery scope can be narrowed using `discovery.mode: filters` (resource groups, regions, tags) or replaced entirely with `discovery.mode: query` for a custom KQL query.
58 - A single job can monitor multiple subscriptions.
59
60 **Runtime (periodic refresh)**
61
62 - Periodically re-discovers resources for **already-active profile types only**.
63 - Controlled by `discovery.refresh_every` (default: 300 seconds, set to 0 to disable).
64
65 > **Important:** Runtime refresh does not activate new profiles. If a new resource type appears after bootstrap, restart the collector to pick it up.
66 limits:
67 description: |
68 - **Minimum collection interval:** 60 seconds (enforced). Azure Monitor metrics granularity is typically 1 minute.
69 - **Metrics reporting delay:** Azure Monitor metrics have a 1-3 minute reporting delay. The collector uses `query_offset` (default: 180s) as a minimum offset and automatically uses a larger effective offset for slower time-grain batches when needed.
70 - **API throttling:** Azure Monitor applies per-subscription rate limits. The collector uses bounded concurrency and batching to stay within limits, but monitoring many resources in a single subscription may require tuning `limits.*` options.
71 performance_impact:
72 description: |
73 The collector batches resources and metrics to minimize Azure API calls and uses bounded concurrency to avoid overwhelming the API.
74
75 **Default concurrency and batching limits:**
76
77 | Setting | Default | Description |
78 |:--------|:--------|:------------|
79 | `limits.max_concurrency` | 4 | Maximum concurrent batch queries |
80 | `limits.max_batch_resources` | 50 | Maximum resources per batch request |
81 | `limits.max_metrics_per_query` | 20 | Maximum metrics per batch request |
82
83 For large deployments, consider splitting resources across multiple jobs. If you hit Azure API rate limits, reduce `max_concurrency`.
84 setup: &setup
85 prerequisites:
86 list:
87 - title: Create an Azure monitoring principal
88 description: |
89 The collector requires a service principal or managed identity with two Azure RBAC roles:
90
91 | Role | Purpose |
92 |:-----|:--------|
93 | **Monitoring Reader** | Access Azure Monitor metrics for target resources |
94 | **Reader** | Query Azure Resource Graph for resource discovery |
95
96 **Option A: Service principal**
97
98 ```bash
99 # Create service principal with Monitoring Reader role
100 az ad sp create-for-rbac --name "netdata-monitor" --role "Monitoring Reader" \
101 --scopes /subscriptions/<subscription-id>
102
103 # Add the Reader role for resource discovery
104 az role assignment create --assignee <appId-from-above> \
105 --role "Reader" --scope /subscriptions/<subscription-id>
106
107 # Note the appId (client_id), password (client_secret), and tenant
108 ```
109
110 **Option B: Managed identity** (Azure VMs, VMSS, or AKS)
111
112 ```bash
113 # Assign both roles to the VM's managed identity
114 az role assignment create --assignee <managed-identity-principal-id> \
115 --role "Monitoring Reader" --scope /subscriptions/<subscription-id>
116
117 az role assignment create --assignee <managed-identity-principal-id> \
118 --role "Reader" --scope /subscriptions/<subscription-id>
119 ```
120 configuration:
121 file:
122 name: go.d/azure_monitor.conf
123 options:
124 description: |
125 The following options can be defined globally: `update_every`, `autodetection_retry`.
126
127 **Profile file locations:**
128
129 | Type | Path |
130 |:-----|:-----|
131 | Stock profiles | `/usr/lib/netdata/conf.d/go.d/azure_monitor.profiles/default/` |
132 | User overrides | `/etc/netdata/go.d/azure_monitor.profiles/` |
133
134 User profile files with the same basename as a [stock profile](https://github.com/netdata/netdata/tree/master/src/go/plugin/go.d/config/go.d/azure_monitor.profiles/default) override it.
135 Custom profiles extend the collector's catalog -- they do not replace the discovery mechanism.
136 folding:
137 title: Config options
138 enabled: true
139 list:
140 - name: update_every
141 description: Data collection interval (seconds). Must be at least 60.
142 default_value: 60
143 required: false
144 group: Collection
145 - name: autodetection_retry
146 description: Autodetection retry interval (seconds). Set 0 to disable.
147 default_value: 0
148 required: false
149 group: Collection
150 - name: subscription_ids
151 description: List of Azure subscription IDs to monitor. Used as the scope for resource discovery.
152 default_value: ""
153 required: true
154 group: Collection
155 - name: cloud
156 description: "Azure cloud environment: `public`, `government`, or `china`."
157 default_value: public
158 required: false
159 group: Collection
160 - name: query_offset
161 description: Minimum offset (seconds) subtracted from metric query windows. Increase if metrics appear incomplete.
162 default_value: 180
163 required: false
164 group: Collection
165 detailed_description: |
166 Azure Monitor metrics have a built-in reporting delay of 1-3 minutes. The collector subtracts this offset from the current time when building metric query windows to avoid fetching incomplete data points.
167
168 The configured `query_offset` acts as a minimum floor. For slower metric batches, the collector automatically uses a larger effective offset when the batch time grain is longer than the configured value.
169
170 - **Default (180s)** works for most services.
171 - **Longer time grains** (for example `PT5M`) automatically use at least one full time grain as the effective offset.
172 - **Increase to 240-300s** if you still see gaps or missing data points.
173 - **Do not set below 60s** -- metrics will likely be incomplete.
174 - name: timeout
175 description: Timeout for Azure Resource Graph and Azure Monitor API requests, in seconds.
176 default_value: 30
177 required: false
178 group: Collection
179 - name: auth.mode
180 description: "Authentication method: `service_principal`, `managed_identity`, or `default`."
181 default_value: ""
182 required: true
183 group: Authentication
184 detailed_description: |
185 Determines how the collector authenticates with Azure.
186
187 | Mode | When to use | Required options |
188 |:-----|:------------|:-----------------|
189 | `service_principal` | Running outside Azure, or when you need explicit credentials | `tenant_id`, `client_id`, `client_secret` |
190 | `managed_identity` | Running on Azure VMs, VMSS, or AKS with a managed identity | Optionally `client_id` for user-assigned identity |
191 | `default` | Uses the Azure SDK default credential chain (environment variables, managed identity, Azure CLI, etc.) | None |
192 - name: auth.mode_service_principal.tenant_id
193 description: Entra ID tenant ID (required for `service_principal` mode).
194 default_value: ""
195 required: false
196 group: Authentication
197 - name: auth.mode_service_principal.client_id
198 description: Entra ID application (client) ID (required for `service_principal` mode).
199 default_value: ""
200 required: false
201 group: Authentication
202 - name: auth.mode_service_principal.client_secret
203 description: Entra ID client secret (required for `service_principal` mode).
204 default_value: ""
205 required: false
206 group: Authentication
207 - name: auth.mode_managed_identity.client_id
208 description: Client ID for user-assigned managed identity. Leave empty for system-assigned.
209 default_value: ""
210 required: false
211 group: Authentication
212 - name: discovery.refresh_every
213 description: Interval (seconds) for refreshing discovered resources. Set `0` to disable runtime re-discovery after bootstrap.
214 default_value: 300
215 required: false
216 group: Discovery
217 - name: discovery.mode
218 description: "Resource discovery method: `filters` (structured filters) or `query` (custom KQL)."
219 default_value: filters
220 required: false
221 group: Discovery
222 detailed_description: |
223 Controls how the collector finds candidate Azure resources.
224
225 | Mode | Behavior |
226 |:-----|:---------|
227 | `filters` | Builds an Azure Resource Graph query from the structured `mode_filters.*` options (resource groups, regions, tags). This is the default. |
228 | `query` | Uses the raw KQL you provide in `discovery.mode_query.kql`. The query must project `id`, `name`, `type`, `resourceGroup`, and `location`. Project `tags` too when using `virtual_nodes.by_resource_tag`. |
229 - name: discovery.mode_filters.resource_groups
230 description: Optional list of Azure resource groups to include in `filters` mode.
231 default_value: "[]"
232 required: false
233 group: Discovery
234 - name: discovery.mode_filters.regions
235 description: Optional list of Azure regions to include in `filters` mode.
236 default_value: "[]"
237 required: false
238 group: Discovery
239 - name: discovery.mode_filters.tags
240 description: Optional exact-match tag filters for `filters` mode. Keys are matched case-insensitively and values case-sensitively.
241 default_value: "{}"
242 required: false
243 group: Discovery
244 - name: discovery.mode_query.kql
245 description: Custom Azure Resource Graph KQL for `query` mode. Must project `id`, `name`, `type`, `resourceGroup`, `location`; project `tags` too when using `virtual_nodes.by_resource_tag`.
246 default_value: ""
247 required: false
248 group: Discovery
249 detailed_description: |
250 A raw Azure Resource Graph KQL query used when `discovery.mode` is `query`.
251 See the [Azure Resource Graph query language documentation](https://learn.microsoft.com/en-us/azure/governance/resource-graph/concepts/query-language) for syntax and supported operators.
252
253 The query **must** project these five columns:
254
255 | Column | Description |
256 |:-------|:------------|
257 | `id` | Full Azure resource ID (ARM format) |
258 | `name` | Resource name |
259 | `type` | Resource type (e.g., `microsoft.sql/servers/databases`) |
260 | `resourceGroup` | Resource group name |
261 | `location` | Azure region |
262
263 If `virtual_nodes.by_resource_tag` is set, also project `tags`. Missing `tags` or non-object-shaped `tags` do not fail discovery; affected resources fall back to the default job host scope and the collector logs a warning once per successful discovery refresh.
264
265 :::info
266
267 - Returned resource `type` values should match the Azure resource types expected by the active profiles.
268 - Resources with unsupported or non-matching types are ignored and do not activate profiles.
269 - For the stock catalog, see [built-in profiles](https://github.com/netdata/netdata/tree/master/src/go/plugin/go.d/config/go.d/azure_monitor.profiles/default).
270
271 :::
272
273 Example:
274
275 ```
276 resources
277 | where tags.env =~ "prod"
278 | project id, name, type, resourceGroup, location, tags
279 ```
280 - name: profiles.mode
281 description: "How profiles are selected: `auto` (discover from resources), `exact` (explicit list), or `combined` (both)."
282 default_value: auto
283 required: false
284 group: Profiles
285 detailed_description: |
286 Controls how the collector decides which metric profiles to activate.
287
288 | Mode | Behavior |
289 |:-----|:---------|
290 | `auto` | Discovers resource types in your subscriptions and enables matching [built-in profiles](https://github.com/netdata/netdata/tree/master/src/go/plugin/go.d/config/go.d/azure_monitor.profiles/default) automatically. This is the default. |
291 | `exact` | Uses only the profile entries listed under `profiles.mode_exact.entries`. No auto-discovery. |
292 | `combined` | Merges auto-discovered profiles with the explicit entries listed under `profiles.mode_combined.entries`. |
293
294 Each profile entry uses `name` as the canonical profile basename. The basename is the profile filename without the `.yaml` / `.yml` suffix and must be lowercase.
295
296 Filter layering:
297
298 - `discovery.mode_filters.*` defines the job-wide discovery scope.
299 - `profiles.mode_*.entries[].filters.*` narrows resources for one profile only.
300 - The effective resource set for a profile is the intersection of both filter sets.
301 - Per-profile filters never widen or bypass the global discovery scope.
302 - In `discovery.mode: query`, per-profile filters can use only `resource_groups` and `regions`. If you need per-profile tag filtering there, encode it in the KQL.
303 - name: profiles.mode_auto.entries
304 description: Optional per-profile overrides applied only to profiles that auto-activate at bootstrap.
305 default_value: "[]"
306 required: false
307 group: Profiles
308 detailed_description: |
309 Each entry has:
310
311 | Field | Description |
312 |:------|:------------|
313 | `name` | Canonical profile basename. |
314 | `filters.resource_groups` | Optional resource-group narrowing for this profile. |
315 | `filters.regions` | Optional region narrowing for this profile. |
316 | `filters.tags` | Optional tag narrowing for this profile in `discovery.mode: filters`. |
317
318 Auto-mode entries do not activate profiles on their own. They only override filtering for profiles that were auto-selected at bootstrap.
319 In `discovery.mode: query`, only `filters.resource_groups` and `filters.regions` apply.
320 - name: profiles.mode_exact.entries
321 description: Explicit profile entries used by `exact` mode.
322 default_value: "[]"
323 required: false
324 group: Profiles
325 detailed_description: |
326 Each entry has:
327
328 | Field | Description |
329 |:------|:------------|
330 | `name` | Canonical profile basename. |
331 | `filters.resource_groups` | Optional resource-group narrowing for this profile. |
332 | `filters.regions` | Optional region narrowing for this profile. |
333 | `filters.tags` | Optional tag narrowing for this profile in `discovery.mode: filters`. |
334
335 Per-profile filters only narrow the globally discovered resource set. They never widen it.
336 In `discovery.mode: query`, only `filters.resource_groups` and `filters.regions` apply.
337 - name: profiles.mode_combined.entries
338 description: Explicit profile entries merged with auto-discovered profiles in `combined` mode.
339 default_value: "[]"
340 required: false
341 group: Profiles
342 detailed_description: |
343 Each entry has:
344
345 | Field | Description |
346 |:------|:------------|
347 | `name` | Canonical profile basename. |
348 | `filters.resource_groups` | Optional resource-group narrowing for this profile. |
349 | `filters.regions` | Optional region narrowing for this profile. |
350 | `filters.tags` | Optional tag narrowing for this profile in `discovery.mode: filters`. |
351
352 If an explicit `combined` entry matches an auto-selected profile, the collector keeps one runtime profile and overlays the explicit entry filters onto it.
353 In `discovery.mode: query`, only `filters.resource_groups` and `filters.regions` apply.
354 - name: limits.max_concurrency
355 description: Maximum concurrent batch queries to Azure Monitor.
356 default_value: 4
357 required: false
358 group: Limits
359 - name: limits.max_batch_resources
360 description: Maximum resources per Azure Monitor batch request.
361 default_value: 50
362 required: false
363 group: Limits
364 - name: limits.max_metrics_per_query
365 description: Maximum metrics per Azure Monitor batch request.
366 default_value: 20
367 required: false
368 group: Limits
369 - name: vnode
370 description: Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes).
371 default_value: ""
372 required: false
373 group: Virtual Node
374 detailed_description: |
375 This job-level virtual node is used for metrics written to the default host scope.
376 If `virtual_nodes.by_resource_tag` is also set, resources that have a safe value for the configured tag are routed to workload virtual nodes instead. Resources without that tag, with an empty value, or with an unsafe hostname value continue to use the job-level `vnode` when configured.
377 - name: virtual_nodes.by_resource_tag
378 description: Creates workload virtual nodes from an Azure resource tag value.
379 default_value: ""
380 required: false
381 group: Virtual Node
382 detailed_description: |
383 Set this to an Azure resource tag key, for example `workload`, to route resource metrics under virtual nodes named after that tag value.
384
385 - Tag keys are matched case-insensitively; tag values keep their Azure case and are trimmed.
386 - Empty or missing tag values use the default job host scope.
387 - Unsafe hostname values use the default job host scope and are summarized in a warning once per successful discovery refresh.
388 - The virtual node GUID is deterministic from `azure_monitor:` plus the trimmed tag value, so the same Azure workload value maps to the same Azure Monitor virtual node across jobs and subscriptions.
389 - Virtual node metadata includes `_vnode_type=azure_workload`. Netdata also adds `_hostname` when emitting the virtual node definition.
390 - Workload virtual nodes increase host and alert cardinality. Health alerts defined for Azure Monitor charts attach per workload virtual node.
391 - The metrix scoped vec cache grows with observed workload scope and label cardinality during the collector runtime; keep the configured tag's cardinality bounded by operator policy.
392 examples:
393 folding:
394 title: Config
395 enabled: true
396 list:
397 - name: Service principal with structured discovery
398 description: Authenticate with a service principal and auto-discover resources across two subscriptions, filtered to the `production-rg` resource group in `eastus` with the tag `env=prod`.
399 folding:
400 enabled: false
401 config: |
402 jobs:
403 - name: prod
404 subscription_ids:
405 - "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
406 - "bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb"
407 discovery:
408 mode: filters
409 mode_filters:
410 resource_groups:
411 - production-rg
412 regions:
413 - eastus
414 tags:
415 env:
416 - prod
417 profiles:
418 mode: auto
419 auth:
420 mode: service_principal
421 mode_service_principal:
422 tenant_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
423 client_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
424 client_secret: "your-client-secret"
425 - name: Workload virtual nodes from resource tags
426 description: Route resources with `tags.workload` to virtual nodes named after the workload value. Resources without the tag stay on the default job host scope.
427 config: |
428 jobs:
429 - name: prod-workloads
430 subscription_ids:
431 - "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
432 virtual_nodes:
433 by_resource_tag: workload
434 discovery:
435 mode: filters
436 profiles:
437 mode: auto
438 auth:
439 mode: service_principal
440 mode_service_principal:
441 tenant_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
442 client_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
443 client_secret: "your-client-secret"
444 - name: Custom KQL with workload virtual nodes
445 description: In `query` discovery mode, project `tags` so `virtual_nodes.by_resource_tag` can derive workload virtual nodes.
446 config: |
447 jobs:
448 - name: prod-query-workloads
449 subscription_ids:
450 - "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
451 virtual_nodes:
452 by_resource_tag: workload
453 discovery:
454 mode: query
455 mode_query:
456 kql: |
457 resources
458 | where tags.env =~ "prod"
459 | project id, name, type, resourceGroup, location, tags
460 profiles:
461 mode: auto
462 auth:
463 mode: default
464 - name: Job virtual node plus workload virtual nodes
465 description: Use a job-level `vnode` as the default host scope while tagged resources route to workload virtual nodes.
466 config: |
467 jobs:
468 - name: prod-with-fallback-node
469 vnode: azure-fallback-node
470 subscription_ids:
471 - "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
472 virtual_nodes:
473 by_resource_tag: workload
474 discovery:
475 mode: filters
476 profiles:
477 mode: auto
478 auth:
479 mode: managed_identity
480 - name: Managed identity with exact profiles
481 description: Use a managed identity (on an Azure VM, VMSS, or AKS) and monitor only SQL Database and PostgreSQL Flexible Server resources -- skip auto-discovery of other services.
482 config: |
483 jobs:
484 - name: databases
485 subscription_ids:
486 - "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
487 profiles:
488 mode: exact
489 mode_exact:
490 entries:
491 - name: sql_database
492 - name: postgres_flexible
493 auth:
494 mode: managed_identity
495 - name: Global and per-profile filters together
496 description: Apply a global discovery boundary to the whole job, then narrow only the SQL Database profile further with a per-profile tag filter.
497 config: |
498 jobs:
499 - name: prod-databases
500 subscription_ids:
501 - "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
502 discovery:
503 mode: filters
504 mode_filters:
505 resource_groups:
506 - production-rg
507 regions:
508 - eastus
509 profiles:
510 mode: combined
511 mode_combined:
512 entries:
513 - name: sql_database
514 filters:
515 tags:
516 env:
517 - prod
518 # Effective scope:
519 # 1. Discovery first keeps only resources in production-rg and eastus.
520 # 2. Auto-selected profiles use that global scope as-is.
521 # 3. The sql_database profile is narrowed further to resources tagged env=prod.
522 # 4. The sql_database profile cannot see resources outside production-rg/eastus,
523 # because per-profile filters only narrow the globally discovered set.
524 auth:
525 mode: managed_identity
526 - name: Custom Azure Resource Graph KQL
527 description: Replace the built-in discovery filters with your own KQL query. Useful when you need joins, computed columns, or filtering logic that structured filters cannot express.
528 config: |
529 jobs:
530 - name: prod-query
531 subscription_ids:
532 - "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
533 discovery:
534 mode: query
535 mode_query:
536 kql: |
537 resources
538 | where tags.env =~ "prod"
539 | project id, name, type, resourceGroup, location, tags
540 profiles:
541 mode: auto
542 auth:
543 mode: default
544 - name: Azure Government cloud
545 description: "Connect to an Azure Government environment. Set `cloud: government` to use the correct authentication and API endpoints."
546 config: |
547 jobs:
548 - name: gov
549 subscription_ids:
550 - "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
551 cloud: government
552 auth:
553 mode: service_principal
554 mode_service_principal:
555 tenant_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
556 client_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
557 client_secret: "your-client-secret"
558 troubleshooting: &troubleshooting
559 problems:
560 list:
561 - name: No metrics are collected
562 description: |
563 Check the following:
564
565 - **Permissions** -- The principal has both **Monitoring Reader** and **Reader** roles on the target subscription.
566 - **Subscription IDs** -- The `subscription_ids` list includes the correct subscription(s).
567 - **Resources are active** -- Verify in Azure Portal > Metrics that the resources are producing metrics.
568 - **Collector logs** -- Check for authentication or API errors:
569 ```bash
570 # systemd
571 journalctl -u netdata --namespace=netdata --grep azure_monitor --since "5 minutes ago"
572 # non-systemd
573 grep azure_monitor /var/log/netdata/collector.log
574 ```
575 - name: Missing metrics for some resource types
576 description: |
577 Profiles are matched by Azure resource type. If a resource type exists but metrics are missing:
578
579 - **Check profile mode** -- Ensure `profiles.mode: auto` (default), or explicitly list the profile basename under `profiles.mode_exact.entries` or `profiles.mode_combined.entries`.
580 - **Verify a [built-in profile](https://github.com/netdata/netdata/tree/master/src/go/plugin/go.d/config/go.d/azure_monitor.profiles/default) exists** -- List available profiles:
581 ```bash
582 ls /usr/lib/netdata/conf.d/go.d/azure_monitor.profiles/default/
583 ```
584 - **Check resource activity** -- Some metrics only appear when the resource is actively processing data (e.g., IoT Hub telemetry metrics require devices to be sending messages).
585 - **New resource types after startup** -- Runtime discovery does not activate new profiles. Restart the collector if new resource types were added after bootstrap.
586 - name: Charts have gaps or incomplete data
587 description: |
588 Azure Monitor metrics have a built-in reporting delay of **1-3 minutes**.
589
590 - The collector uses `query_offset` (default: **180 seconds**) as the minimum offset for metric query windows.
591 - Slower time-grain batches automatically use a larger effective offset when needed.
592 - If metrics are still missing or incomplete, increase `query_offset` to **240** or **300** seconds.
593 - name: Workload virtual nodes are not created
594 description: |
595 When `virtual_nodes.by_resource_tag` is set, check the discovered resource tags:
596
597 - The configured tag key is matched case-insensitively, but the value must be non-empty after trimming.
598 - In `discovery.mode: query`, the KQL must project `tags`. If the `tags` column is missing or not an object, the collector logs a warning and affected resources use the default job host scope.
599 - Tag values must be safe Netdata hostnames. Unsafe values are summarized in a warning once per successful discovery refresh and affected resources use the default job host scope.
600 - The same Azure workload value intentionally maps to the same Azure Monitor virtual node across subscriptions and jobs. Use distinct tag values when tenants should remain separate.
601 - Azure Monitor namespaces workload GUID input with `azure_monitor:` to avoid accidental collisions with other collectors that derive virtual node GUIDs from hostnames.
602 - name: More alerts appear after enabling workload virtual nodes
603 description: |
604 Workload virtual nodes multiply the host scope of Azure Monitor charts. Health alerts attached to those charts evaluate per workload virtual node, so alert volume can increase with the number of distinct workload tag values.
605 - name: Authentication errors in sovereign clouds
606 description: |
607 For Azure Government or Azure China clouds, set the `cloud` parameter:
608
609 - Azure Government: `cloud: government`
610 - Azure China (21Vianet): `cloud: china`
611
612 Ensure the service principal is registered in the correct cloud tenant.
613 alerts: &alerts []
614 metrics: &metrics
615 folding:
616 title: Metrics
617 enabled: false
618 description: |
619 The metrics collected depend on which Azure Monitor profiles are active. Each profile corresponds to an Azure service (e.g., SQL Database, Virtual Machines) and defines the specific charts and metrics for that service.
620
621 With the default `profiles.mode: auto`, profiles are activated automatically based on the resource types found in your subscriptions.
622
623 **See the service-specific integrations below for detailed metric lists per Azure service.**
624 availability: []
625 scopes: []
626 - <<: *module
627 meta:
628 <<: *meta
629 id: collector-go.d.plugin-azure_monitor-sql_managed_instance
630 monitored_instance:
631 name: Azure SQL Managed Instance
632 link: https://learn.microsoft.com/azure/azure-sql/managed-instance/
633 icon_filename: azure.svg
634 categories:
635 - data-collection.cloud-and-devops
636 keywords:
637 - azure
638 - sql
639 - managed
640 - instance
641 - database
642 - mssql
643 overview:
644 <<: *overview
645 data_collection:
646 metrics_description: |
647 :::info
648
649 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
650
651 :::
652
653 Monitor Azure SQL Managed Instance with metrics covering:
654
655 - **Compute** -- CPU utilization (average/max), virtual core count
656 - **Storage** -- reserved and used storage
657 - **I/O** -- read/write throughput, I/O request rate
658 method_description: *method_description
659 alerts:
660 - name: am_sql_managed_instance_cpu
661 metric: azure_monitor.sql_managed_instance.cpu
662 info: "SQL MI CPU utilization on ${label:resource_name}"
663 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_managed_instance.conf
664 - name: am_sql_managed_instance_storage_utilization
665 metric: azure_monitor.sql_managed_instance.storage
666 info: "SQL MI storage utilization on ${label:resource_name}"
667 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_managed_instance.conf
668 - name: am_sql_managed_instance_io_requests
669 metric: azure_monitor.sql_managed_instance.io_requests
670 info: "SQL MI I/O requests on ${label:resource_name}"
671 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_managed_instance.conf
672 metrics:
673 folding:
674 title: Metrics
675 enabled: false
676 description: ""
677 availability: []
678 scopes:
679 - name: resource
680 description: "These metrics refer to each monitored Azure resource."
681 labels:
682 - name: resource_name
683 description: "The Azure resource name."
684 - name: resource_group
685 description: "The Azure resource group."
686 - name: region
687 description: "The Azure region where the resource is deployed."
688 - name: resource_type
689 description: "The Azure resource type identifier."
690 - name: profile
691 description: "The Azure Monitor profile basename."
692 - name: subscription_id
693 description: "The Azure subscription identifier."
694 - name: resource_uid
695 description: "The unique Azure resource identifier."
696 metrics:
697 - name: azure_monitor.sql_managed_instance.cpu
698 description: Azure SQL Managed Instance CPU Utilization
699 unit: percentage
700 chart_type: line
701 dimensions:
702 - name: average
703 - name: maximum
704 - name: azure_monitor.sql_managed_instance.io_throughput
705 description: Azure SQL Managed Instance I/O Throughput
706 unit: bytes/s
707 chart_type: line
708 dimensions:
709 - name: read
710 - name: written
711 - name: azure_monitor.sql_managed_instance.io_requests
712 description: Azure SQL Managed Instance I/O Requests
713 unit: requests/s
714 chart_type: line
715 dimensions:
716 - name: average
717 - name: azure_monitor.sql_managed_instance.storage
718 description: Azure SQL Managed Instance Storage
719 unit: MiB
720 chart_type: line
721 dimensions:
722 - name: reserved
723 - name: used
724 - name: azure_monitor.sql_managed_instance.virtual_core_count
725 description: Azure SQL Managed Instance Virtual Core Count
726 unit: cores
727 chart_type: line
728 dimensions:
729 - name: average
730 - <<: *module
731 meta:
732 <<: *meta
733 id: collector-go.d.plugin-azure_monitor-sql_database
734 monitored_instance:
735 name: Azure SQL Database
736 link: https://learn.microsoft.com/azure/azure-sql/database/
737 icon_filename: azure.svg
738 categories:
739 - data-collection.cloud-and-devops
740 keywords:
741 - azure
742 - sql
743 - database
744 - mssql
745 - dtu
746 overview:
747 <<: *overview
748 data_collection:
749 metrics_description: |
750 :::info
751
752 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
753
754 :::
755
756 Monitor Azure SQL Database with metrics covering:
757
758 - **CPU and DTU** -- CPU utilization (average/max), instance CPU, DTU consumption, vCore usage
759 - **Memory** -- instance memory utilization
760 - **Storage** -- data and allocated storage, storage utilization, tempdb size, in-memory OLTP storage
761 - **I/O** -- data read and log write utilization, tempdb log utilization
762 - **Connections** -- successful, failed, and firewall-blocked connections, active sessions and workers
763 - **Availability** -- database availability percentage
764 - **Advanced** -- deadlocks, replication lag, serverless CPU/memory/billing, ledger digest, free tier usage
765 method_description: *method_description
766 alerts:
767 - name: am_sql_database_availability
768 metric: azure_monitor.sql_database.availability
769 info: "SQL Database availability on ${label:resource_name}"
770 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
771 - name: am_sql_database_cpu
772 metric: azure_monitor.sql_database.cpu
773 info: "SQL Database CPU on ${label:resource_name}"
774 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
775 - name: am_sql_database_instance_cpu
776 metric: azure_monitor.sql_database.instance_cpu
777 info: "SQL Database instance CPU on ${label:resource_name}"
778 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
779 - name: am_sql_database_instance_memory
780 metric: azure_monitor.sql_database.instance_memory
781 info: "SQL Database instance memory on ${label:resource_name}"
782 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
783 - name: am_sql_database_dtu_consumption
784 metric: azure_monitor.sql_database.dtu_consumption
785 info: "SQL Database DTU consumption on ${label:resource_name}"
786 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
787 - name: am_sql_database_data_io
788 metric: azure_monitor.sql_database.io_utilization
789 info: "SQL Database data I/O on ${label:resource_name}"
790 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
791 - name: am_sql_database_log_write
792 metric: azure_monitor.sql_database.io_utilization
793 info: "SQL Database log write I/O on ${label:resource_name}"
794 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
795 - name: am_sql_database_workers
796 metric: azure_monitor.sql_database.resource_utilization
797 info: "SQL Database worker utilization on ${label:resource_name}"
798 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
799 - name: am_sql_database_sessions
800 metric: azure_monitor.sql_database.resource_utilization
801 info: "SQL Database session utilization on ${label:resource_name}"
802 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
803 - name: am_sql_database_connection_failures
804 metric: azure_monitor.sql_database.connections
805 info: "SQL Database system connection failures on ${label:resource_name}"
806 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
807 - name: am_sql_database_firewall_blocks
808 metric: azure_monitor.sql_database.connections
809 info: "SQL Database firewall blocks on ${label:resource_name}"
810 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
811 - name: am_sql_database_deadlocks
812 metric: azure_monitor.sql_database.deadlocks
813 info: "SQL Database deadlocks on ${label:resource_name}"
814 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
815 - name: am_sql_database_storage_utilization
816 metric: azure_monitor.sql_database.storage_utilization
817 info: "SQL Database storage utilization on ${label:resource_name}"
818 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
819 - name: am_sql_database_xtp_storage
820 metric: azure_monitor.sql_database.xtp_storage
821 info: "SQL Database In-Memory OLTP storage on ${label:resource_name}"
822 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
823 - name: am_sql_database_tempdb_log_utilization
824 metric: azure_monitor.sql_database.tempdb_log_utilization
825 info: "SQL Database tempdb log utilization on ${label:resource_name}"
826 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
827 - name: am_sql_database_replication_lag
828 metric: azure_monitor.sql_database.replication_lag
829 info: "SQL Database replication lag on ${label:resource_name}"
830 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
831 - name: am_sql_database_serverless_cpu
832 metric: azure_monitor.sql_database.serverless_utilization
833 info: "SQL Database serverless CPU on ${label:resource_name}"
834 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
835 - name: am_sql_database_serverless_memory
836 metric: azure_monitor.sql_database.serverless_utilization
837 info: "SQL Database serverless memory on ${label:resource_name}"
838 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
839 - name: am_sql_database_ledger_digest_failures
840 metric: azure_monitor.sql_database.ledger_digest
841 info: "SQL Database ledger digest failures on ${label:resource_name}"
842 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf
843 metrics:
844 folding:
845 title: Metrics
846 enabled: false
847 description: ""
848 availability: []
849 scopes:
850 - name: resource
851 description: "These metrics refer to each monitored Azure resource."
852 labels:
853 - name: resource_name
854 description: "The Azure resource name."
855 - name: resource_group
856 description: "The Azure resource group."
857 - name: region
858 description: "The Azure region where the resource is deployed."
859 - name: resource_type
860 description: "The Azure resource type identifier."
861 - name: profile
862 description: "The Azure Monitor profile basename."
863 - name: subscription_id
864 description: "The Azure subscription identifier."
865 - name: resource_uid
866 description: "The unique Azure resource identifier."
867 metrics:
868 - name: azure_monitor.sql_database.cpu
869 description: Azure SQL Database CPU Utilization
870 unit: percentage
871 chart_type: line
872 dimensions:
873 - name: average
874 - name: maximum
875 - name: azure_monitor.sql_database.instance_cpu
876 description: Azure SQL Database Instance CPU Utilization
877 unit: percentage
878 chart_type: line
879 dimensions:
880 - name: average
881 - name: azure_monitor.sql_database.instance_memory
882 description: Azure SQL Database Instance Memory Utilization
883 unit: percentage
884 chart_type: line
885 dimensions:
886 - name: average
887 - name: azure_monitor.sql_database.dtu_consumption
888 description: Azure SQL Database DTU Consumption
889 unit: percentage
890 chart_type: line
891 dimensions:
892 - name: average
893 - name: azure_monitor.sql_database.io_utilization
894 description: Azure SQL Database I/O Utilization
895 unit: percentage
896 chart_type: line
897 dimensions:
898 - name: data_read
899 - name: log_write
900 - name: azure_monitor.sql_database.resource_utilization
901 description: Azure SQL Database Resource Utilization
902 unit: percentage
903 chart_type: line
904 dimensions:
905 - name: workers
906 - name: sessions
907 - name: azure_monitor.sql_database.availability
908 description: Azure SQL Database Availability
909 unit: percentage
910 chart_type: line
911 dimensions:
912 - name: average
913 - name: azure_monitor.sql_database.connections
914 description: Azure SQL Database Connection Events
915 unit: connections/s
916 chart_type: line
917 dimensions:
918 - name: successful
919 - name: failed_system
920 - name: failed_user
921 - name: firewall_blocked
922 - name: azure_monitor.sql_database.deadlocks
923 description: Azure SQL Database Deadlocks
924 unit: deadlocks/s
925 chart_type: line
926 dimensions:
927 - name: total
928 - name: azure_monitor.sql_database.storage
929 description: Azure SQL Database Storage
930 unit: bytes
931 chart_type: line
932 dimensions:
933 - name: used
934 - name: allocated
935 - name: azure_monitor.sql_database.storage_utilization
936 description: Azure SQL Database Storage Utilization
937 unit: percentage
938 chart_type: line
939 dimensions:
940 - name: average
941 - name: azure_monitor.sql_database.tempdb_size
942 description: Azure SQL Database Tempdb Size
943 unit: KiB
944 chart_type: line
945 dimensions:
946 - name: data
947 - name: log
948 - name: azure_monitor.sql_database.tempdb_log_utilization
949 description: Azure SQL Database Tempdb Log Utilization
950 unit: percentage
951 chart_type: line
952 dimensions:
953 - name: average
954 - name: azure_monitor.sql_database.vcore_usage
955 description: Azure SQL Database vCore Usage
956 unit: vCores
957 chart_type: line
958 dimensions:
959 - name: used
960 - name: limit
961 - name: azure_monitor.sql_database.dtu_usage
962 description: Azure SQL Database DTU Usage
963 unit: DTU
964 chart_type: line
965 dimensions:
966 - name: used
967 - name: limit
968 - name: azure_monitor.sql_database.sessions_count
969 description: Azure SQL Database Sessions Count
970 unit: sessions
971 chart_type: line
972 dimensions:
973 - name: average
974 - name: azure_monitor.sql_database.replication_lag
975 description: Azure SQL Database Replication Lag
976 unit: seconds
977 chart_type: line
978 dimensions:
979 - name: average
980 - name: azure_monitor.sql_database.xtp_storage
981 description: Azure SQL Database In-Memory OLTP Storage
982 unit: percentage
983 chart_type: line
984 dimensions:
985 - name: average
986 - name: azure_monitor.sql_database.serverless_utilization
987 description: Azure SQL Database Serverless Utilization
988 unit: percentage
989 chart_type: line
990 dimensions:
991 - name: cpu
992 - name: memory
993 - name: azure_monitor.sql_database.serverless_billing
994 description: Azure SQL Database Serverless Billing
995 unit: vCore-seconds/s
996 chart_type: line
997 dimensions:
998 - name: total
999 - name: ha_replicas
1000 - name: azure_monitor.sql_database.free_tier_usage
1001 description: Azure SQL Database Free Tier Usage
1002 unit: vCore-seconds
1003 chart_type: line
1004 dimensions:
1005 - name: consumed
1006 - name: remaining
1007 - name: azure_monitor.sql_database.ledger_digest
1008 description: Azure SQL Database Ledger Digest Uploads
1009 unit: events/s
1010 chart_type: line
1011 dimensions:
1012 - name: success
1013 - name: failed
1014 - <<: *module
1015 meta:
1016 <<: *meta
1017 id: collector-go.d.plugin-azure_monitor-postgres_flexible
1018 monitored_instance:
1019 name: Azure PostgreSQL Flexible Server
1020 link: https://learn.microsoft.com/azure/postgresql/flexible-server/
1021 icon_filename: azure.svg
1022 categories:
1023 - data-collection.cloud-and-devops
1024 keywords:
1025 - azure
1026 - postgresql
1027 - postgres
1028 - database
1029 - flexible
1030 overview:
1031 <<: *overview
1032 data_collection:
1033 metrics_description: |
1034 :::info
1035
1036 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
1037
1038 :::
1039
1040 Monitor Azure PostgreSQL Flexible Server with metrics covering:
1041
1042 - **Compute** -- CPU utilization, burstable CPU credits (consumed/remaining)
1043 - **Memory** -- memory utilization
1044 - **Storage** -- storage used/free, backup storage, WAL storage, database size, disk queue depth and saturation
1045 - **I/O** -- IOPS (read/write), disk throughput, temp bytes/files
1046 - **Connections** -- active connections, connection rate, max connections, PgBouncer client/server/pooled connections
1047 - **Database** -- transaction rate, commits/rollbacks, tuple reads/writes, replication lag (time/bytes), deadlocks
1048 - **Maintenance** -- autovacuum operations, table coverage, bloat percentage, buffer cache hit rate
1049 - **Sessions** -- sessions by state and wait event type, backend count
1050 - **Availability** -- database alive state
1051 method_description: *method_description
1052 alerts:
1053 - name: am_postgres_flexible_availability
1054 metric: azure_monitor.postgres_flexible.availability
1055 info: "PostgreSQL Flexible Server down on ${label:resource_name}"
1056 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1057 - name: am_postgres_flexible_cpu
1058 metric: azure_monitor.postgres_flexible.cpu
1059 info: "PostgreSQL Flexible CPU on ${label:resource_name}"
1060 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1061 - name: am_postgres_flexible_memory
1062 metric: azure_monitor.postgres_flexible.memory
1063 info: "PostgreSQL Flexible memory on ${label:resource_name}"
1064 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1065 - name: am_postgres_flexible_storage_utilization
1066 metric: azure_monitor.postgres_flexible.storage_utilization
1067 info: "PostgreSQL Flexible storage on ${label:resource_name}"
1068 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1069 - name: am_postgres_flexible_disk_bandwidth_saturation
1070 metric: azure_monitor.postgres_flexible.disk_saturation
1071 info: "PostgreSQL Flexible disk bandwidth saturation on ${label:resource_name}"
1072 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1073 - name: am_postgres_flexible_disk_iops_saturation
1074 metric: azure_monitor.postgres_flexible.disk_saturation
1075 info: "PostgreSQL Flexible disk IOPS saturation on ${label:resource_name}"
1076 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1077 - name: am_postgres_flexible_disk_queue_depth
1078 metric: azure_monitor.postgres_flexible.disk_queue_depth
1079 info: "PostgreSQL Flexible disk queue depth on ${label:resource_name}"
1080 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1081 - name: am_postgres_flexible_failed_connections
1082 metric: azure_monitor.postgres_flexible.connection_rate
1083 info: "PostgreSQL Flexible failed connections on ${label:resource_name}"
1084 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1085 - name: am_postgres_flexible_tcp_connection_backlog
1086 metric: azure_monitor.postgres_flexible.tcp_connection_backlog
1087 info: "PostgreSQL Flexible TCP connection backlog on ${label:resource_name}"
1088 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1089 - name: am_postgres_flexible_deadlocks
1090 metric: azure_monitor.postgres_flexible.deadlocks
1091 info: "PostgreSQL Flexible deadlocks on ${label:resource_name}"
1092 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1093 - name: am_postgres_flexible_rollback_ratio
1094 metric: azure_monitor.postgres_flexible.transactions
1095 info: "PostgreSQL Flexible rollback ratio on ${label:resource_name}"
1096 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1097 - name: am_postgres_flexible_longest_query
1098 metric: azure_monitor.postgres_flexible.long_running
1099 info: "PostgreSQL Flexible long running query on ${label:resource_name}"
1100 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1101 - name: am_postgres_flexible_longest_transaction
1102 metric: azure_monitor.postgres_flexible.long_running
1103 info: "PostgreSQL Flexible long running transaction on ${label:resource_name}"
1104 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1105 - name: am_postgres_flexible_xid_usage
1106 metric: azure_monitor.postgres_flexible.xid_usage
1107 info: "PostgreSQL Flexible transaction ID usage on ${label:resource_name}"
1108 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1109 - name: am_postgres_flexible_xmin_age
1110 metric: azure_monitor.postgres_flexible.xmin_age
1111 info: "PostgreSQL Flexible backend xmin age on ${label:resource_name}"
1112 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1113 - name: am_postgres_flexible_bloat
1114 metric: azure_monitor.postgres_flexible.bloat
1115 info: "PostgreSQL Flexible table bloat on ${label:resource_name}"
1116 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1117 - name: am_postgres_flexible_replication_lag
1118 metric: azure_monitor.postgres_flexible.replication_lag_time
1119 info: "PostgreSQL Flexible replication lag on ${label:resource_name}"
1120 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1121 - name: am_postgres_flexible_cpu_credits_remaining
1122 metric: azure_monitor.postgres_flexible.cpu_credits
1123 info: "PostgreSQL Flexible CPU credits low on ${label:resource_name}"
1124 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1125 - name: am_postgres_flexible_temp_bytes
1126 metric: azure_monitor.postgres_flexible.temp_bytes
1127 info: "PostgreSQL Flexible temp file I/O on ${label:resource_name}"
1128 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf
1129 metrics:
1130 folding:
1131 title: Metrics
1132 enabled: false
1133 description: ""
1134 availability: []
1135 scopes:
1136 - name: resource
1137 description: "These metrics refer to each monitored Azure resource."
1138 labels:
1139 - name: resource_name
1140 description: "The Azure resource name."
1141 - name: resource_group
1142 description: "The Azure resource group."
1143 - name: region
1144 description: "The Azure region where the resource is deployed."
1145 - name: resource_type
1146 description: "The Azure resource type identifier."
1147 - name: profile
1148 description: "The Azure Monitor profile basename."
1149 - name: subscription_id
1150 description: "The Azure subscription identifier."
1151 - name: resource_uid
1152 description: "The unique Azure resource identifier."
1153 metrics:
1154 - name: azure_monitor.postgres_flexible.cpu
1155 description: Azure PostgreSQL Flexible Server CPU Utilization
1156 unit: percentage
1157 chart_type: line
1158 dimensions:
1159 - name: average
1160 - name: azure_monitor.postgres_flexible.memory
1161 description: Azure PostgreSQL Flexible Server Memory Utilization
1162 unit: percentage
1163 chart_type: line
1164 dimensions:
1165 - name: average
1166 - name: azure_monitor.postgres_flexible.availability
1167 description: Azure PostgreSQL Flexible Server Database Alive
1168 unit: state
1169 chart_type: line
1170 dimensions:
1171 - name: maximum
1172 - name: azure_monitor.postgres_flexible.iops
1173 description: Azure PostgreSQL Flexible Server IOPS
1174 unit: operations/s
1175 chart_type: line
1176 dimensions:
1177 - name: total
1178 - name: read
1179 - name: write
1180 - name: azure_monitor.postgres_flexible.disk_throughput
1181 description: Azure PostgreSQL Flexible Server Disk Throughput
1182 unit: bytes/s
1183 chart_type: line
1184 dimensions:
1185 - name: read
1186 - name: write
1187 - name: azure_monitor.postgres_flexible.disk_saturation
1188 description: Azure PostgreSQL Flexible Server Disk Saturation
1189 unit: percentage
1190 chart_type: line
1191 dimensions:
1192 - name: bandwidth
1193 - name: iops
1194 - name: azure_monitor.postgres_flexible.disk_queue_depth
1195 description: Azure PostgreSQL Flexible Server Disk Queue Depth
1196 unit: operations
1197 chart_type: line
1198 dimensions:
1199 - name: average
1200 - name: azure_monitor.postgres_flexible.buffer_cache
1201 description: Azure PostgreSQL Flexible Server Buffer Cache
1202 unit: blocks/s
1203 chart_type: line
1204 dimensions:
1205 - name: hits
1206 - name: reads
1207 - name: azure_monitor.postgres_flexible.active_connections
1208 description: Azure PostgreSQL Flexible Server Active Connections
1209 unit: connections
1210 chart_type: line
1211 dimensions:
1212 - name: average
1213 - name: azure_monitor.postgres_flexible.connection_rate
1214 description: Azure PostgreSQL Flexible Server Connection Rate
1215 unit: connections/s
1216 chart_type: line
1217 dimensions:
1218 - name: succeeded
1219 - name: failed
1220 - name: azure_monitor.postgres_flexible.transactions
1221 description: Azure PostgreSQL Flexible Server Transactions
1222 unit: transactions/s
1223 chart_type: line
1224 dimensions:
1225 - name: committed
1226 - name: rolled_back
1227 - name: azure_monitor.postgres_flexible.transaction_rate
1228 description: Azure PostgreSQL Flexible Server Transaction Rate
1229 unit: transactions/s
1230 chart_type: line
1231 dimensions:
1232 - name: total
1233 - name: xact_total
1234 - name: azure_monitor.postgres_flexible.deadlocks
1235 description: Azure PostgreSQL Flexible Server Deadlocks
1236 unit: deadlocks/s
1237 chart_type: line
1238 dimensions:
1239 - name: total
1240 - name: azure_monitor.postgres_flexible.tuple_reads
1241 description: Azure PostgreSQL Flexible Server Tuple Reads
1242 unit: tuples/s
1243 chart_type: line
1244 dimensions:
1245 - name: returned
1246 - name: fetched
1247 - name: azure_monitor.postgres_flexible.tuple_writes
1248 description: Azure PostgreSQL Flexible Server Tuple Writes
1249 unit: tuples/s
1250 chart_type: line
1251 dimensions:
1252 - name: inserted
1253 - name: updated
1254 - name: deleted
1255 - name: azure_monitor.postgres_flexible.temp_files
1256 description: Azure PostgreSQL Flexible Server Temp Files Created
1257 unit: files/s
1258 chart_type: line
1259 dimensions:
1260 - name: total
1261 - name: azure_monitor.postgres_flexible.temp_bytes
1262 description: Azure PostgreSQL Flexible Server Temp Bytes Written
1263 unit: bytes/s
1264 chart_type: line
1265 dimensions:
1266 - name: total
1267 - name: azure_monitor.postgres_flexible.long_running
1268 description: Azure PostgreSQL Flexible Server Long Running Operations
1269 unit: seconds
1270 chart_type: line
1271 dimensions:
1272 - name: query
1273 - name: transaction
1274 - name: azure_monitor.postgres_flexible.xid_usage
1275 description: Azure PostgreSQL Flexible Server Transaction ID Usage
1276 unit: transactions
1277 chart_type: line
1278 dimensions:
1279 - name: max_used
1280 - name: oldest_xmin
1281 - name: azure_monitor.postgres_flexible.xmin_age
1282 description: Azure PostgreSQL Flexible Server Backend XID Age
1283 unit: transactions
1284 chart_type: line
1285 dimensions:
1286 - name: maximum
1287 - name: azure_monitor.postgres_flexible.network
1288 description: Azure PostgreSQL Flexible Server Network Traffic
1289 unit: bytes/s
1290 chart_type: line
1291 dimensions:
1292 - name: in
1293 - name: out
1294 - name: azure_monitor.postgres_flexible.storage
1295 description: Azure PostgreSQL Flexible Server Storage
1296 unit: bytes
1297 chart_type: line
1298 dimensions:
1299 - name: used
1300 - name: free
1301 - name: azure_monitor.postgres_flexible.storage_utilization
1302 description: Azure PostgreSQL Flexible Server Storage Utilization
1303 unit: percentage
1304 chart_type: line
1305 dimensions:
1306 - name: average
1307 - name: azure_monitor.postgres_flexible.wal_storage
1308 description: Azure PostgreSQL Flexible Server WAL Storage
1309 unit: bytes
1310 chart_type: line
1311 dimensions:
1312 - name: used
1313 - name: azure_monitor.postgres_flexible.database_size
1314 description: Azure PostgreSQL Flexible Server Database Size
1315 unit: bytes
1316 chart_type: line
1317 dimensions:
1318 - name: average
1319 - name: azure_monitor.postgres_flexible.backup_storage
1320 description: Azure PostgreSQL Flexible Server Backup Storage
1321 unit: bytes
1322 chart_type: line
1323 dimensions:
1324 - name: used
1325 - name: azure_monitor.postgres_flexible.replication_lag_time
1326 description: Azure PostgreSQL Flexible Server Replication Lag
1327 unit: seconds
1328 chart_type: line
1329 dimensions:
1330 - name: average
1331 - name: azure_monitor.postgres_flexible.replication_lag_bytes
1332 description: Azure PostgreSQL Flexible Server Replication Lag Bytes
1333 unit: bytes
1334 chart_type: line
1335 dimensions:
1336 - name: physical
1337 - name: logical
1338 - name: azure_monitor.postgres_flexible.sessions_by_state
1339 description: Azure PostgreSQL Flexible Server Sessions by State
1340 unit: sessions
1341 chart_type: line
1342 dimensions:
1343 - name: maximum
1344 - name: azure_monitor.postgres_flexible.sessions_by_wait_event_type
1345 description: Azure PostgreSQL Flexible Server Sessions by Wait Event Type
1346 unit: sessions
1347 chart_type: line
1348 dimensions:
1349 - name: maximum
1350 - name: azure_monitor.postgres_flexible.autovacuum_operations
1351 description: Azure PostgreSQL Flexible Server Autovacuum Operations
1352 unit: operations
1353 chart_type: line
1354 dimensions:
1355 - name: vacuum
1356 - name: autovacuum
1357 - name: analyze
1358 - name: autoanalyze
1359 - name: azure_monitor.postgres_flexible.autovacuum_table_coverage
1360 description: Azure PostgreSQL Flexible Server Autovacuum Table Coverage
1361 unit: tables
1362 chart_type: line
1363 dimensions:
1364 - name: vacuumed
1365 - name: autovacuumed
1366 - name: analyzed
1367 - name: autoanalyzed
1368 - name: total
1369 - name: azure_monitor.postgres_flexible.tuple_liveness
1370 description: Azure PostgreSQL Flexible Server Tuple Liveness
1371 unit: tuples
1372 chart_type: line
1373 dimensions:
1374 - name: live
1375 - name: dead
1376 - name: modified_since_analyze
1377 - name: azure_monitor.postgres_flexible.bloat
1378 description: Azure PostgreSQL Flexible Server Table Bloat
1379 unit: percentage
1380 chart_type: line
1381 dimensions:
1382 - name: maximum
1383 - name: azure_monitor.postgres_flexible.backend_count
1384 description: Azure PostgreSQL Flexible Server Backend Count
1385 unit: connections
1386 chart_type: line
1387 dimensions:
1388 - name: maximum
1389 - name: azure_monitor.postgres_flexible.pgbouncer_client_connections
1390 description: Azure PostgreSQL Flexible Server PgBouncer Client Connections
1391 unit: connections
1392 chart_type: line
1393 dimensions:
1394 - name: active
1395 - name: waiting
1396 - name: azure_monitor.postgres_flexible.pgbouncer_server_connections
1397 description: Azure PostgreSQL Flexible Server PgBouncer Server Connections
1398 unit: connections
1399 chart_type: line
1400 dimensions:
1401 - name: active
1402 - name: idle
1403 - name: azure_monitor.postgres_flexible.pgbouncer_pool_count
1404 description: Azure PostgreSQL Flexible Server PgBouncer Pool Count
1405 unit: pools
1406 chart_type: line
1407 dimensions:
1408 - name: pools
1409 - name: azure_monitor.postgres_flexible.pgbouncer_pooled_connections
1410 description: Azure PostgreSQL Flexible Server PgBouncer Pooled Connections
1411 unit: connections
1412 chart_type: line
1413 dimensions:
1414 - name: pooled_connections
1415 - name: azure_monitor.postgres_flexible.cpu_credits
1416 description: Azure PostgreSQL Flexible Server CPU Credits
1417 unit: credits
1418 chart_type: line
1419 dimensions:
1420 - name: consumed
1421 - name: remaining
1422 - name: azure_monitor.postgres_flexible.postmaster_cpu
1423 description: Azure PostgreSQL Flexible Server Postmaster CPU Usage
1424 unit: percentage
1425 chart_type: line
1426 dimensions:
1427 - name: average
1428 - name: azure_monitor.postgres_flexible.max_connections
1429 description: Azure PostgreSQL Flexible Server Max Connections
1430 unit: connections
1431 chart_type: line
1432 dimensions:
1433 - name: maximum
1434 - name: azure_monitor.postgres_flexible.tcp_connection_backlog
1435 description: Azure PostgreSQL Flexible Server TCP Connection Backlog
1436 unit: connections
1437 chart_type: line
1438 dimensions:
1439 - name: maximum
1440 - <<: *module
1441 meta:
1442 <<: *meta
1443 id: collector-go.d.plugin-azure_monitor-cosmos_db
1444 monitored_instance:
1445 name: Azure Cosmos DB Account
1446 link: https://learn.microsoft.com/azure/cosmos-db/
1447 icon_filename: azure.svg
1448 categories:
1449 - data-collection.cloud-and-devops
1450 keywords:
1451 - azure
1452 - cosmos
1453 - cosmosdb
1454 - nosql
1455 - database
1456 - documentdb
1457 overview:
1458 <<: *overview
1459 data_collection:
1460 metrics_description: |
1461 :::info
1462
1463 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
1464
1465 :::
1466
1467 Monitor Azure Cosmos DB with metrics covering:
1468
1469 - **Request units** -- RU consumption, provisioned throughput (provisioned/autoscale), normalized RU per partition
1470 - **Storage** -- data, index, and quota storage, physical partition size
1471 - **Latency** -- server-side latency (direct/gateway), replication latency
1472 - **Requests** -- total requests, API requests (Mongo/Cassandra/Gremlin), metadata requests, dedicated gateway requests
1473 - **Availability** -- service availability percentage
1474 - **Advanced** -- document count, partition count, dedicated gateway CPU/memory, integrated cache hit rate
1475 method_description: *method_description
1476 alerts:
1477 - name: am_cosmos_db_availability
1478 metric: azure_monitor.cosmos_db.availability
1479 info: "Cosmos DB availability on ${label:resource_name}"
1480 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1481 - name: am_cosmos_db_normalized_ru_consumption
1482 metric: azure_monitor.cosmos_db.normalized_ru_consumption
1483 info: "Cosmos DB RU consumption on ${label:resource_name}"
1484 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1485 - name: am_cosmos_db_storage_utilization
1486 metric: azure_monitor.cosmos_db.storage
1487 info: "Cosmos DB storage utilization on ${label:resource_name}"
1488 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1489 - name: am_cosmos_db_server_side_latency_direct
1490 metric: azure_monitor.cosmos_db.server_side_latency
1491 info: "Cosmos DB direct latency on ${label:resource_name}"
1492 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1493 - name: am_cosmos_db_server_side_latency_gateway
1494 metric: azure_monitor.cosmos_db.server_side_latency
1495 info: "Cosmos DB gateway latency on ${label:resource_name}"
1496 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1497 - name: am_cosmos_db_replication_latency
1498 metric: azure_monitor.cosmos_db.replication_latency
1499 info: "Cosmos DB replication latency on ${label:resource_name}"
1500 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1501 - name: am_cosmos_db_dedicated_gateway_cpu
1502 metric: azure_monitor.cosmos_db.dedicated_gateway_cpu
1503 info: "Cosmos DB dedicated gateway CPU on ${label:resource_name}"
1504 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1505 - name: am_cosmos_db_integrated_cache_item_hit_rate
1506 metric: azure_monitor.cosmos_db.integrated_cache_hit_rate
1507 info: "Cosmos DB cache item hit rate on ${label:resource_name}"
1508 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1509 - name: am_cosmos_db_integrated_cache_query_hit_rate
1510 metric: azure_monitor.cosmos_db.integrated_cache_hit_rate
1511 info: "Cosmos DB cache query hit rate on ${label:resource_name}"
1512 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1513 - name: am_cosmos_db_cassandra_connection_closures
1514 metric: azure_monitor.cosmos_db.cassandra_connections
1515 info: "Cosmos DB Cassandra connection closures on ${label:resource_name}"
1516 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf
1517 metrics:
1518 folding:
1519 title: Metrics
1520 enabled: false
1521 description: ""
1522 availability: []
1523 scopes:
1524 - name: resource
1525 description: "These metrics refer to each monitored Azure resource."
1526 labels:
1527 - name: resource_name
1528 description: "The Azure resource name."
1529 - name: resource_group
1530 description: "The Azure resource group."
1531 - name: region
1532 description: "The Azure region where the resource is deployed."
1533 - name: resource_type
1534 description: "The Azure resource type identifier."
1535 - name: profile
1536 description: "The Azure Monitor profile basename."
1537 - name: subscription_id
1538 description: "The Azure subscription identifier."
1539 - name: resource_uid
1540 description: "The unique Azure resource identifier."
1541 metrics:
1542 - name: azure_monitor.cosmos_db.total_requests
1543 description: Azure Cosmos DB Total Requests
1544 unit: requests/s
1545 chart_type: line
1546 dimensions:
1547 - name: count
1548 - name: azure_monitor.cosmos_db.request_units
1549 description: Azure Cosmos DB Request Units Consumed
1550 unit: RU/s
1551 chart_type: line
1552 dimensions:
1553 - name: total
1554 - name: azure_monitor.cosmos_db.normalized_ru_consumption
1555 description: Azure Cosmos DB Normalized RU Consumption
1556 unit: percentage
1557 chart_type: line
1558 dimensions:
1559 - name: maximum
1560 - name: azure_monitor.cosmos_db.server_side_latency
1561 description: Azure Cosmos DB Server-Side Latency
1562 unit: milliseconds
1563 chart_type: line
1564 dimensions:
1565 - name: direct
1566 - name: gateway
1567 - name: azure_monitor.cosmos_db.replication_latency
1568 description: Azure Cosmos DB Replication Latency
1569 unit: milliseconds
1570 chart_type: line
1571 dimensions:
1572 - name: average
1573 - name: azure_monitor.cosmos_db.storage
1574 description: Azure Cosmos DB Storage
1575 unit: bytes
1576 chart_type: line
1577 dimensions:
1578 - name: data
1579 - name: index
1580 - name: quota
1581 - name: azure_monitor.cosmos_db.document_count
1582 description: Azure Cosmos DB Document Count
1583 unit: documents
1584 chart_type: line
1585 dimensions:
1586 - name: average
1587 - name: azure_monitor.cosmos_db.partition_size
1588 description: Azure Cosmos DB Physical Partition Size
1589 unit: bytes
1590 chart_type: line
1591 dimensions:
1592 - name: maximum
1593 - name: azure_monitor.cosmos_db.partition_count
1594 description: Azure Cosmos DB Physical Partition Count
1595 unit: partitions
1596 chart_type: line
1597 dimensions:
1598 - name: maximum
1599 - name: azure_monitor.cosmos_db.provisioned_throughput
1600 description: Azure Cosmos DB Provisioned Throughput
1601 unit: RU/s
1602 chart_type: line
1603 dimensions:
1604 - name: provisioned
1605 - name: autoscale_max
1606 - name: autoscaled
1607 - name: azure_monitor.cosmos_db.partition_throughput
1608 description: Azure Cosmos DB Physical Partition Throughput
1609 unit: RU/s
1610 chart_type: line
1611 dimensions:
1612 - name: maximum
1613 - name: azure_monitor.cosmos_db.availability
1614 description: Azure Cosmos DB Service Availability
1615 unit: percentage
1616 chart_type: line
1617 dimensions:
1618 - name: average
1619 - name: azure_monitor.cosmos_db.metadata_requests
1620 description: Azure Cosmos DB Metadata Requests
1621 unit: requests/s
1622 chart_type: line
1623 dimensions:
1624 - name: count
1625 - name: azure_monitor.cosmos_db.api_requests
1626 description: Azure Cosmos DB API Requests
1627 unit: requests/s
1628 chart_type: line
1629 dimensions:
1630 - name: mongo
1631 - name: cassandra
1632 - name: gremlin
1633 - name: azure_monitor.cosmos_db.api_request_charges
1634 description: Azure Cosmos DB API Request Charges
1635 unit: RU/s
1636 chart_type: line
1637 dimensions:
1638 - name: mongo
1639 - name: cassandra
1640 - name: gremlin
1641 - name: azure_monitor.cosmos_db.cassandra_connections
1642 description: Azure Cosmos DB Cassandra Connection Closures
1643 unit: connections/s
1644 chart_type: line
1645 dimensions:
1646 - name: total
1647 - name: azure_monitor.cosmos_db.dedicated_gateway_cpu
1648 description: Azure Cosmos DB Dedicated Gateway CPU Usage
1649 unit: percentage
1650 chart_type: line
1651 dimensions:
1652 - name: average
1653 - name: azure_monitor.cosmos_db.dedicated_gateway_memory
1654 description: Azure Cosmos DB Dedicated Gateway Memory Usage
1655 unit: bytes
1656 chart_type: line
1657 dimensions:
1658 - name: average
1659 - name: azure_monitor.cosmos_db.dedicated_gateway_requests
1660 description: Azure Cosmos DB Dedicated Gateway Requests
1661 unit: requests/s
1662 chart_type: line
1663 dimensions:
1664 - name: count
1665 - name: azure_monitor.cosmos_db.integrated_cache_hit_rate
1666 description: Azure Cosmos DB Integrated Cache Hit Rate
1667 unit: percentage
1668 chart_type: line
1669 dimensions:
1670 - name: item
1671 - name: query
1672 - <<: *module
1673 meta:
1674 <<: *meta
1675 id: collector-go.d.plugin-azure_monitor-logic_apps
1676 monitored_instance:
1677 name: Azure Logic Apps Workflow
1678 link: https://learn.microsoft.com/azure/logic-apps/
1679 icon_filename: azure.svg
1680 categories:
1681 - data-collection.cloud-and-devops
1682 keywords:
1683 - azure
1684 - logic
1685 - apps
1686 - workflow
1687 - integration
1688 - automation
1689 overview:
1690 <<: *overview
1691 data_collection:
1692 metrics_description: |
1693 :::info
1694
1695 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
1696
1697 :::
1698
1699 Monitor Azure Logic Apps with metrics covering:
1700
1701 - **Runs** -- run lifecycle (started/completed/succeeded/failed/cancelled), run failure rate
1702 - **Actions** -- action lifecycle (started/completed/succeeded/failed/skipped)
1703 - **Triggers** -- trigger lifecycle (started/completed/succeeded/fired/failed/skipped)
1704 - **Latency** -- run, action, and trigger latency
1705 - **Billing** -- billable executions (total/actions/triggers), billing by type (native/connector/storage)
1706 - **Throttling** -- run, action, and trigger throttling events
1707 method_description: *method_description
1708 alerts:
1709 - name: am_logic_apps_run_failure_rate
1710 metric: azure_monitor.logic_apps.run_failure_rate
1711 info: "Logic Apps run failure rate on ${label:resource_name}"
1712 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1713 - name: am_logic_apps_runs_failed
1714 metric: azure_monitor.logic_apps.run_lifecycle
1715 info: "Logic Apps failed runs on ${label:resource_name}"
1716 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1717 - name: am_logic_apps_run_latency
1718 metric: azure_monitor.logic_apps.run_latency
1719 info: "Logic Apps run latency on ${label:resource_name}"
1720 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1721 - name: am_logic_apps_run_throttled
1722 metric: azure_monitor.logic_apps.run_throttling
1723 info: "Logic Apps run throttling on ${label:resource_name}"
1724 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1725 - name: am_logic_apps_actions_failed
1726 metric: azure_monitor.logic_apps.action_lifecycle
1727 info: "Logic Apps failed actions on ${label:resource_name}"
1728 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1729 - name: am_logic_apps_action_latency
1730 metric: azure_monitor.logic_apps.action_latency
1731 info: "Logic Apps action latency on ${label:resource_name}"
1732 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1733 - name: am_logic_apps_action_throttled
1734 metric: azure_monitor.logic_apps.action_throttling
1735 info: "Logic Apps action throttling on ${label:resource_name}"
1736 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1737 - name: am_logic_apps_triggers_failed
1738 metric: azure_monitor.logic_apps.trigger_lifecycle
1739 info: "Logic Apps failed triggers on ${label:resource_name}"
1740 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1741 - name: am_logic_apps_trigger_latency
1742 metric: azure_monitor.logic_apps.trigger_latency
1743 info: "Logic Apps trigger latency on ${label:resource_name}"
1744 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1745 - name: am_logic_apps_trigger_throttled
1746 metric: azure_monitor.logic_apps.trigger_throttling
1747 info: "Logic Apps trigger throttling on ${label:resource_name}"
1748 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1749 - name: am_logic_apps_completion_token_overflow
1750 metric: azure_monitor.logic_apps.agent
1751 info: "Logic Apps completion token overflow on ${label:resource_name}"
1752 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1753 - name: am_logic_apps_prompt_token_overflow
1754 metric: azure_monitor.logic_apps.agent
1755 info: "Logic Apps prompt token overflow on ${label:resource_name}"
1756 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf
1757 metrics:
1758 folding:
1759 title: Metrics
1760 enabled: false
1761 description: ""
1762 availability: []
1763 scopes:
1764 - name: resource
1765 description: "These metrics refer to each monitored Azure resource."
1766 labels:
1767 - name: resource_name
1768 description: "The Azure resource name."
1769 - name: resource_group
1770 description: "The Azure resource group."
1771 - name: region
1772 description: "The Azure region where the resource is deployed."
1773 - name: resource_type
1774 description: "The Azure resource type identifier."
1775 - name: profile
1776 description: "The Azure Monitor profile basename."
1777 - name: subscription_id
1778 description: "The Azure subscription identifier."
1779 - name: resource_uid
1780 description: "The unique Azure resource identifier."
1781 metrics:
1782 - name: azure_monitor.logic_apps.run_lifecycle
1783 description: Azure Logic Apps Run Lifecycle
1784 unit: runs/s
1785 chart_type: line
1786 dimensions:
1787 - name: started
1788 - name: completed
1789 - name: succeeded
1790 - name: failed
1791 - name: cancelled
1792 - name: azure_monitor.logic_apps.run_latency
1793 description: Azure Logic Apps Run Latency
1794 unit: seconds
1795 chart_type: line
1796 dimensions:
1797 - name: all
1798 - name: success
1799 - name: azure_monitor.logic_apps.run_failure_rate
1800 description: Azure Logic Apps Run Failure Rate
1801 unit: percentage
1802 chart_type: line
1803 dimensions:
1804 - name: failure_rate
1805 - name: azure_monitor.logic_apps.run_throttling
1806 description: Azure Logic Apps Run Throttling
1807 unit: events/s
1808 chart_type: line
1809 dimensions:
1810 - name: during_run
1811 - name: at_start
1812 - name: azure_monitor.logic_apps.action_lifecycle
1813 description: Azure Logic Apps Action Lifecycle
1814 unit: actions/s
1815 chart_type: line
1816 dimensions:
1817 - name: started
1818 - name: completed
1819 - name: succeeded
1820 - name: failed
1821 - name: skipped
1822 - name: azure_monitor.logic_apps.action_latency
1823 description: Azure Logic Apps Action Latency
1824 unit: seconds
1825 chart_type: line
1826 dimensions:
1827 - name: all
1828 - name: success
1829 - name: azure_monitor.logic_apps.action_throttling
1830 description: Azure Logic Apps Action Throttling
1831 unit: events/s
1832 chart_type: line
1833 dimensions:
1834 - name: total
1835 - name: azure_monitor.logic_apps.trigger_lifecycle
1836 description: Azure Logic Apps Trigger Lifecycle
1837 unit: triggers/s
1838 chart_type: line
1839 dimensions:
1840 - name: started
1841 - name: completed
1842 - name: succeeded
1843 - name: fired
1844 - name: failed
1845 - name: skipped
1846 - name: azure_monitor.logic_apps.trigger_latency
1847 description: Azure Logic Apps Trigger Latency
1848 unit: seconds
1849 chart_type: line
1850 dimensions:
1851 - name: all
1852 - name: fire
1853 - name: success
1854 - name: azure_monitor.logic_apps.trigger_throttling
1855 description: Azure Logic Apps Trigger Throttling
1856 unit: events/s
1857 chart_type: line
1858 dimensions:
1859 - name: total
1860 - name: azure_monitor.logic_apps.billable_executions
1861 description: Azure Logic Apps Billable Executions
1862 unit: executions/s
1863 chart_type: line
1864 dimensions:
1865 - name: total
1866 - name: actions
1867 - name: triggers
1868 - name: azure_monitor.logic_apps.billing_by_type
1869 description: Azure Logic Apps Billing by Type
1870 unit: operations/s
1871 chart_type: line
1872 dimensions:
1873 - name: native
1874 - name: standard_connector
1875 - name: storage
1876 - name: azure_monitor.logic_apps.agent
1877 description: Azure Logic Apps AI Agent Activity
1878 unit: events/s
1879 chart_type: line
1880 dimensions:
1881 - name: loop_executions
1882 - name: completion_overflow
1883 - name: prompt_overflow
1884 - <<: *module
1885 meta:
1886 <<: *meta
1887 id: collector-go.d.plugin-azure_monitor-virtual_machines
1888 monitored_instance:
1889 name: Azure Virtual Machine
1890 link: https://learn.microsoft.com/azure/virtual-machines/
1891 icon_filename: azure.svg
1892 categories:
1893 - data-collection.cloud-and-devops
1894 keywords:
1895 - azure
1896 - virtual
1897 - machine
1898 - vm
1899 - compute
1900 - iaas
1901 overview:
1902 <<: *overview
1903 data_collection:
1904 metrics_description: |
1905 :::info
1906
1907 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
1908
1909 :::
1910
1911 Monitor Azure Virtual Machines with metrics covering:
1912
1913 - **Compute** -- CPU utilization, CPU credits (consumed/remaining)
1914 - **Memory** -- available memory (bytes and percentage)
1915 - **Disk** -- IOPS, throughput, latency, and queue depth for OS, data, and temp disks
1916 - **Disk burst** -- burst credits and capacity for OS and data disks, VM-level cached/uncached burst credits
1917 - **Disk cache** -- premium OS and data disk cache hit/miss rates
1918 - **Network** -- traffic in/out, network flows, flow creation rate
1919 - **Availability** -- VM availability state
1920 - **Throttling** -- cached and uncached I/O bandwidth/IOPS throttling
1921 method_description: *method_description
1922 alerts:
1923 - name: am_vm_cpu
1924 metric: azure_monitor.virtual_machines.cpu
1925 info: "VM CPU on ${label:resource_name}"
1926 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1927 - name: am_vm_cpu_credits_remaining
1928 metric: azure_monitor.virtual_machines.cpu_credits
1929 info: "VM CPU credits low on ${label:resource_name}"
1930 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1931 - name: am_vm_memory_available
1932 metric: azure_monitor.virtual_machines.memory_percentage
1933 info: "VM available memory on ${label:resource_name}"
1934 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1935 - name: am_vm_availability
1936 metric: azure_monitor.virtual_machines.availability
1937 info: "VM unavailable ${label:resource_name}"
1938 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1939 - name: am_vm_os_disk_latency
1940 metric: azure_monitor.virtual_machines.os_disk_latency
1941 info: "VM OS disk latency on ${label:resource_name}"
1942 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1943 - name: am_vm_os_disk_queue_depth
1944 metric: azure_monitor.virtual_machines.os_disk_queue_depth
1945 info: "VM OS disk queue depth on ${label:resource_name}"
1946 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1947 - name: am_vm_os_disk_bandwidth_throttling
1948 metric: azure_monitor.virtual_machines.os_disk_throttling
1949 info: "VM OS disk bandwidth throttling on ${label:resource_name}"
1950 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1951 - name: am_vm_os_disk_iops_throttling
1952 metric: azure_monitor.virtual_machines.os_disk_throttling
1953 info: "VM OS disk IOPS throttling on ${label:resource_name}"
1954 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1955 - name: am_vm_os_disk_burst_bps_credits
1956 metric: azure_monitor.virtual_machines.os_disk_burst_credits
1957 info: "VM OS disk burst bandwidth credits on ${label:resource_name}"
1958 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1959 - name: am_vm_os_disk_burst_io_credits
1960 metric: azure_monitor.virtual_machines.os_disk_burst_credits
1961 info: "VM OS disk burst IO credits on ${label:resource_name}"
1962 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1963 - name: am_vm_data_disk_latency
1964 metric: azure_monitor.virtual_machines.data_disk_latency
1965 info: "VM data disk latency on ${label:resource_name}"
1966 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1967 - name: am_vm_data_disk_queue_depth
1968 metric: azure_monitor.virtual_machines.data_disk_queue_depth
1969 info: "VM data disk queue depth on ${label:resource_name}"
1970 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1971 - name: am_vm_data_disk_bandwidth_throttling
1972 metric: azure_monitor.virtual_machines.data_disk_throttling
1973 info: "VM data disk bandwidth throttling on ${label:resource_name}"
1974 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1975 - name: am_vm_data_disk_iops_throttling
1976 metric: azure_monitor.virtual_machines.data_disk_throttling
1977 info: "VM data disk IOPS throttling on ${label:resource_name}"
1978 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1979 - name: am_vm_data_disk_burst_bps_credits
1980 metric: azure_monitor.virtual_machines.data_disk_burst_credits
1981 info: "VM data disk burst bandwidth credits on ${label:resource_name}"
1982 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1983 - name: am_vm_data_disk_burst_io_credits
1984 metric: azure_monitor.virtual_machines.data_disk_burst_credits
1985 info: "VM data disk burst IO credits on ${label:resource_name}"
1986 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1987 - name: am_vm_cached_bandwidth_throttling
1988 metric: azure_monitor.virtual_machines.vm_cached_throttling
1989 info: "VM cached bandwidth throttling on ${label:resource_name}"
1990 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1991 - name: am_vm_cached_iops_throttling
1992 metric: azure_monitor.virtual_machines.vm_cached_throttling
1993 info: "VM cached IOPS throttling on ${label:resource_name}"
1994 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1995 - name: am_vm_uncached_bandwidth_throttling
1996 metric: azure_monitor.virtual_machines.vm_uncached_throttling
1997 info: "VM uncached bandwidth throttling on ${label:resource_name}"
1998 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
1999 - name: am_vm_uncached_iops_throttling
2000 metric: azure_monitor.virtual_machines.vm_uncached_throttling
2001 info: "VM uncached IOPS throttling on ${label:resource_name}"
2002 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
2003 - name: am_vm_cached_burst_bps_credits
2004 metric: azure_monitor.virtual_machines.vm_cached_burst_credits
2005 info: "VM cached burst bandwidth credits on ${label:resource_name}"
2006 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
2007 - name: am_vm_cached_burst_io_credits
2008 metric: azure_monitor.virtual_machines.vm_cached_burst_credits
2009 info: "VM cached burst IO credits on ${label:resource_name}"
2010 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
2011 - name: am_vm_uncached_burst_bps_credits
2012 metric: azure_monitor.virtual_machines.vm_uncached_burst_credits
2013 info: "VM uncached burst bandwidth credits on ${label:resource_name}"
2014 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
2015 - name: am_vm_uncached_burst_io_credits
2016 metric: azure_monitor.virtual_machines.vm_uncached_burst_credits
2017 info: "VM uncached burst IO credits on ${label:resource_name}"
2018 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf
2019 metrics:
2020 folding:
2021 title: Metrics
2022 enabled: false
2023 description: ""
2024 availability: []
2025 scopes:
2026 - name: resource
2027 description: "These metrics refer to each monitored Azure resource."
2028 labels:
2029 - name: resource_name
2030 description: "The Azure resource name."
2031 - name: resource_group
2032 description: "The Azure resource group."
2033 - name: region
2034 description: "The Azure region where the resource is deployed."
2035 - name: resource_type
2036 description: "The Azure resource type identifier."
2037 - name: profile
2038 description: "The Azure Monitor profile basename."
2039 - name: subscription_id
2040 description: "The Azure subscription identifier."
2041 - name: resource_uid
2042 description: "The unique Azure resource identifier."
2043 metrics:
2044 - name: azure_monitor.virtual_machines.cpu
2045 description: Azure Virtual Machine CPU Utilization
2046 unit: percentage
2047 chart_type: line
2048 dimensions:
2049 - name: average
2050 - name: azure_monitor.virtual_machines.cpu_credits
2051 description: Azure Virtual Machine CPU Credits
2052 unit: credits
2053 chart_type: line
2054 dimensions:
2055 - name: consumed
2056 - name: remaining
2057 - name: azure_monitor.virtual_machines.memory
2058 description: Azure Virtual Machine Available Memory
2059 unit: bytes
2060 chart_type: line
2061 dimensions:
2062 - name: available
2063 - name: azure_monitor.virtual_machines.memory_percentage
2064 description: Azure Virtual Machine Available Memory Percentage
2065 unit: percentage
2066 chart_type: line
2067 dimensions:
2068 - name: available
2069 - name: azure_monitor.virtual_machines.availability
2070 description: Azure Virtual Machine Availability
2071 unit: state
2072 chart_type: line
2073 dimensions:
2074 - name: average
2075 - name: azure_monitor.virtual_machines.network_traffic
2076 description: Azure Virtual Machine Network Traffic
2077 unit: bytes/s
2078 chart_type: line
2079 dimensions:
2080 - name: in
2081 - name: out
2082 - name: azure_monitor.virtual_machines.network_flows
2083 description: Azure Virtual Machine Network Flows
2084 unit: flows
2085 chart_type: line
2086 dimensions:
2087 - name: in
2088 - name: out
2089 - name: azure_monitor.virtual_machines.network_flow_creation_rate
2090 description: Azure Virtual Machine Network Flow Creation Rate
2091 unit: flows/s
2092 chart_type: line
2093 dimensions:
2094 - name: in
2095 - name: out
2096 - name: azure_monitor.virtual_machines.disk_throughput
2097 description: Azure Virtual Machine Disk Throughput
2098 unit: bytes/s
2099 chart_type: line
2100 dimensions:
2101 - name: read
2102 - name: write
2103 - name: azure_monitor.virtual_machines.disk_iops
2104 description: Azure Virtual Machine Disk IOPS
2105 unit: operations/s
2106 chart_type: line
2107 dimensions:
2108 - name: read
2109 - name: write
2110 - name: azure_monitor.virtual_machines.os_disk_throughput
2111 description: Azure Virtual Machine OS Disk Throughput
2112 unit: bytes/s
2113 chart_type: line
2114 dimensions:
2115 - name: read
2116 - name: write
2117 - name: azure_monitor.virtual_machines.os_disk_iops
2118 description: Azure Virtual Machine OS Disk IOPS
2119 unit: operations/s
2120 chart_type: line
2121 dimensions:
2122 - name: read
2123 - name: write
2124 - name: azure_monitor.virtual_machines.os_disk_latency
2125 description: Azure Virtual Machine OS Disk Latency
2126 unit: milliseconds
2127 chart_type: line
2128 dimensions:
2129 - name: average
2130 - name: azure_monitor.virtual_machines.os_disk_queue_depth
2131 description: Azure Virtual Machine OS Disk Queue Depth
2132 unit: operations
2133 chart_type: line
2134 dimensions:
2135 - name: average
2136 - name: azure_monitor.virtual_machines.os_disk_throttling
2137 description: Azure Virtual Machine OS Disk Throttling
2138 unit: percentage
2139 chart_type: line
2140 dimensions:
2141 - name: bandwidth
2142 - name: iops
2143 - name: azure_monitor.virtual_machines.os_disk_burst_capacity
2144 description: Azure Virtual Machine OS Disk Burst Capacity
2145 unit: bytes/s
2146 chart_type: line
2147 dimensions:
2148 - name: max_burst
2149 - name: target
2150 - name: azure_monitor.virtual_machines.os_disk_burst_iops_capacity
2151 description: Azure Virtual Machine OS Disk Burst IOPS Capacity
2152 unit: iops
2153 chart_type: line
2154 dimensions:
2155 - name: max_burst
2156 - name: target
2157 - name: azure_monitor.virtual_machines.os_disk_burst_credits
2158 description: Azure Virtual Machine OS Disk Burst Credits Used
2159 unit: percentage
2160 chart_type: line
2161 dimensions:
2162 - name: bandwidth
2163 - name: io
2164 - name: azure_monitor.virtual_machines.data_disk_throughput
2165 description: Azure Virtual Machine Data Disk Throughput
2166 unit: bytes/s
2167 chart_type: line
2168 dimensions:
2169 - name: read
2170 - name: write
2171 - name: azure_monitor.virtual_machines.data_disk_iops
2172 description: Azure Virtual Machine Data Disk IOPS
2173 unit: operations/s
2174 chart_type: line
2175 dimensions:
2176 - name: read
2177 - name: write
2178 - name: azure_monitor.virtual_machines.data_disk_latency
2179 description: Azure Virtual Machine Data Disk Latency
2180 unit: milliseconds
2181 chart_type: line
2182 dimensions:
2183 - name: average
2184 - name: azure_monitor.virtual_machines.data_disk_queue_depth
2185 description: Azure Virtual Machine Data Disk Queue Depth
2186 unit: operations
2187 chart_type: line
2188 dimensions:
2189 - name: average
2190 - name: azure_monitor.virtual_machines.data_disk_throttling
2191 description: Azure Virtual Machine Data Disk Throttling
2192 unit: percentage
2193 chart_type: line
2194 dimensions:
2195 - name: bandwidth
2196 - name: iops
2197 - name: azure_monitor.virtual_machines.data_disk_burst_capacity
2198 description: Azure Virtual Machine Data Disk Burst Capacity
2199 unit: bytes/s
2200 chart_type: line
2201 dimensions:
2202 - name: max_burst
2203 - name: target
2204 - name: azure_monitor.virtual_machines.data_disk_burst_iops_capacity
2205 description: Azure Virtual Machine Data Disk Burst IOPS Capacity
2206 unit: iops
2207 chart_type: line
2208 dimensions:
2209 - name: max_burst
2210 - name: target
2211 - name: azure_monitor.virtual_machines.data_disk_burst_credits
2212 description: Azure Virtual Machine Data Disk Burst Credits Used
2213 unit: percentage
2214 chart_type: line
2215 dimensions:
2216 - name: bandwidth
2217 - name: io
2218 - name: azure_monitor.virtual_machines.temp_disk_throughput
2219 description: Azure Virtual Machine Temp Disk Throughput
2220 unit: bytes/s
2221 chart_type: line
2222 dimensions:
2223 - name: read
2224 - name: write
2225 - name: azure_monitor.virtual_machines.temp_disk_iops
2226 description: Azure Virtual Machine Temp Disk IOPS
2227 unit: operations/s
2228 chart_type: line
2229 dimensions:
2230 - name: read
2231 - name: write
2232 - name: azure_monitor.virtual_machines.temp_disk_latency
2233 description: Azure Virtual Machine Temp Disk Latency
2234 unit: milliseconds
2235 chart_type: line
2236 dimensions:
2237 - name: average
2238 - name: azure_monitor.virtual_machines.temp_disk_queue_depth
2239 description: Azure Virtual Machine Temp Disk Queue Depth
2240 unit: operations
2241 chart_type: line
2242 dimensions:
2243 - name: average
2244 - name: azure_monitor.virtual_machines.premium_data_disk_cache
2245 description: Azure Virtual Machine Premium Data Disk Cache
2246 unit: percentage
2247 chart_type: line
2248 dimensions:
2249 - name: hit
2250 - name: miss
2251 - name: azure_monitor.virtual_machines.premium_os_disk_cache
2252 description: Azure Virtual Machine Premium OS Disk Cache
2253 unit: percentage
2254 chart_type: line
2255 dimensions:
2256 - name: hit
2257 - name: miss
2258 - name: azure_monitor.virtual_machines.vm_cached_throttling
2259 description: Azure Virtual Machine Cached IO Throttling
2260 unit: percentage
2261 chart_type: line
2262 dimensions:
2263 - name: bandwidth
2264 - name: iops
2265 - name: azure_monitor.virtual_machines.vm_uncached_throttling
2266 description: Azure Virtual Machine Uncached IO Throttling
2267 unit: percentage
2268 chart_type: line
2269 dimensions:
2270 - name: bandwidth
2271 - name: iops
2272 - name: azure_monitor.virtual_machines.vm_cached_burst_credits
2273 description: Azure Virtual Machine Cached Burst Credits Used
2274 unit: percentage
2275 chart_type: line
2276 dimensions:
2277 - name: bandwidth
2278 - name: io
2279 - name: azure_monitor.virtual_machines.vm_uncached_burst_credits
2280 description: Azure Virtual Machine Uncached Burst Credits Used
2281 unit: percentage
2282 chart_type: line
2283 dimensions:
2284 - name: bandwidth
2285 - name: io
2286 - <<: *module
2287 meta:
2288 <<: *meta
2289 id: collector-go.d.plugin-azure_monitor-aks
2290 monitored_instance:
2291 name: Azure Kubernetes Service Cluster
2292 link: https://learn.microsoft.com/azure/aks/
2293 icon_filename: azure.svg
2294 categories:
2295 - data-collection.cloud-and-devops
2296 keywords:
2297 - azure
2298 - kubernetes
2299 - aks
2300 - k8s
2301 - containers
2302 - cluster
2303 overview:
2304 <<: *overview
2305 data_collection:
2306 metrics_description: |
2307 :::info
2308
2309 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
2310
2311 :::
2312
2313 Monitor Azure Kubernetes Service (AKS) with metrics covering:
2314
2315 - **Control plane** -- API server CPU/memory, etcd CPU/memory/database utilization, inflight requests
2316 - **Nodes** -- allocatable CPU/memory, per-node CPU (millicores and %), memory (RSS, working set), disk usage, network traffic
2317 - **Pods** -- pods by phase, pods in ready state, node conditions
2318 - **Autoscaler** -- autoscaler health, unneeded nodes, unschedulable pods
2319 method_description: *method_description
2320 alerts:
2321 - name: am_aks_apiserver_cpu
2322 metric: azure_monitor.aks.apiserver_cpu
2323 info: "AKS API server CPU on ${label:resource_name}"
2324 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2325 - name: am_aks_apiserver_memory
2326 metric: azure_monitor.aks.apiserver_memory
2327 info: "AKS API server memory on ${label:resource_name}"
2328 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2329 - name: am_aks_apiserver_inflight_requests
2330 metric: azure_monitor.aks.apiserver_inflight_requests
2331 info: "AKS API server inflight requests on ${label:resource_name}"
2332 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2333 - name: am_aks_etcd_cpu
2334 metric: azure_monitor.aks.etcd_cpu
2335 info: "AKS etcd CPU on ${label:resource_name}"
2336 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2337 - name: am_aks_etcd_memory
2338 metric: azure_monitor.aks.etcd_memory
2339 info: "AKS etcd memory on ${label:resource_name}"
2340 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2341 - name: am_aks_etcd_database
2342 metric: azure_monitor.aks.etcd_database
2343 info: "AKS etcd database usage on ${label:resource_name}"
2344 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2345 - name: am_aks_autoscaler_safe_to_autoscale
2346 metric: azure_monitor.aks.autoscaler_health
2347 info: "AKS autoscaler unsafe on ${label:resource_name}"
2348 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2349 - name: am_aks_autoscaler_unschedulable_pods
2350 metric: azure_monitor.aks.autoscaler_unschedulable_pods
2351 info: "AKS unschedulable pods on ${label:resource_name}"
2352 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2353 - name: am_aks_node_cpu
2354 metric: azure_monitor.aks.node_cpu_percentage
2355 info: "AKS node CPU on ${label:resource_name}"
2356 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2357 - name: am_aks_node_memory_working_set
2358 metric: azure_monitor.aks.node_memory_working_set_percentage
2359 info: "AKS node memory working set on ${label:resource_name}"
2360 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2361 - name: am_aks_node_memory_rss
2362 metric: azure_monitor.aks.node_memory_rss_percentage
2363 info: "AKS node memory RSS on ${label:resource_name}"
2364 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2365 - name: am_aks_node_disk
2366 metric: azure_monitor.aks.node_disk_percentage
2367 info: "AKS node disk usage on ${label:resource_name}"
2368 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf
2369 metrics:
2370 folding:
2371 title: Metrics
2372 enabled: false
2373 description: ""
2374 availability: []
2375 scopes:
2376 - name: resource
2377 description: "These metrics refer to each monitored Azure resource."
2378 labels:
2379 - name: resource_name
2380 description: "The Azure resource name."
2381 - name: resource_group
2382 description: "The Azure resource group."
2383 - name: region
2384 description: "The Azure region where the resource is deployed."
2385 - name: resource_type
2386 description: "The Azure resource type identifier."
2387 - name: profile
2388 description: "The Azure Monitor profile basename."
2389 - name: subscription_id
2390 description: "The Azure subscription identifier."
2391 - name: resource_uid
2392 description: "The unique Azure resource identifier."
2393 metrics:
2394 - name: azure_monitor.aks.apiserver_cpu
2395 description: AKS API Server CPU Utilization
2396 unit: percentage
2397 chart_type: line
2398 dimensions:
2399 - name: average
2400 - name: maximum
2401 - name: azure_monitor.aks.apiserver_memory
2402 description: AKS API Server Memory Utilization
2403 unit: percentage
2404 chart_type: line
2405 dimensions:
2406 - name: average
2407 - name: maximum
2408 - name: azure_monitor.aks.apiserver_inflight_requests
2409 description: AKS API Server Inflight Requests
2410 unit: requests
2411 chart_type: line
2412 dimensions:
2413 - name: average
2414 - name: azure_monitor.aks.etcd_cpu
2415 description: AKS etcd CPU Utilization
2416 unit: percentage
2417 chart_type: line
2418 dimensions:
2419 - name: average
2420 - name: maximum
2421 - name: azure_monitor.aks.etcd_memory
2422 description: AKS etcd Memory Utilization
2423 unit: percentage
2424 chart_type: line
2425 dimensions:
2426 - name: average
2427 - name: maximum
2428 - name: azure_monitor.aks.etcd_database
2429 description: AKS etcd Database Utilization
2430 unit: percentage
2431 chart_type: line
2432 dimensions:
2433 - name: average
2434 - name: maximum
2435 - name: azure_monitor.aks.pod_status_phase
2436 description: AKS Pods by Phase
2437 unit: pods
2438 chart_type: line
2439 dimensions:
2440 - name: average
2441 - name: azure_monitor.aks.pod_status_ready
2442 description: AKS Pods in Ready State
2443 unit: pods
2444 chart_type: line
2445 dimensions:
2446 - name: average
2447 - name: azure_monitor.aks.allocatable_cpu
2448 description: AKS Allocatable CPU Cores
2449 unit: cores
2450 chart_type: line
2451 dimensions:
2452 - name: average
2453 - name: azure_monitor.aks.allocatable_memory
2454 description: AKS Allocatable Memory
2455 unit: bytes
2456 chart_type: line
2457 dimensions:
2458 - name: average
2459 - name: azure_monitor.aks.node_conditions
2460 description: AKS Node Conditions
2461 unit: nodes
2462 chart_type: line
2463 dimensions:
2464 - name: average
2465 - name: azure_monitor.aks.autoscaler_health
2466 description: AKS Cluster Autoscaler Health
2467 unit: state
2468 chart_type: line
2469 dimensions:
2470 - name: safe_to_autoscale
2471 - name: cooldown
2472 - name: azure_monitor.aks.autoscaler_unschedulable_pods
2473 description: AKS Autoscaler Unschedulable Pods
2474 unit: pods
2475 chart_type: line
2476 dimensions:
2477 - name: average
2478 - name: azure_monitor.aks.autoscaler_unneeded_nodes
2479 description: AKS Autoscaler Unneeded Nodes
2480 unit: nodes
2481 chart_type: line
2482 dimensions:
2483 - name: average
2484 - name: azure_monitor.aks.node_cpu_millicores
2485 description: AKS Node CPU Usage
2486 unit: millicores
2487 chart_type: line
2488 dimensions:
2489 - name: average
2490 - name: maximum
2491 - name: azure_monitor.aks.node_cpu_percentage
2492 description: AKS Node CPU Percentage
2493 unit: percentage
2494 chart_type: line
2495 dimensions:
2496 - name: average
2497 - name: maximum
2498 - name: azure_monitor.aks.node_memory_working_set
2499 description: AKS Node Memory Working Set
2500 unit: bytes
2501 chart_type: line
2502 dimensions:
2503 - name: average
2504 - name: maximum
2505 - name: azure_monitor.aks.node_memory_working_set_percentage
2506 description: AKS Node Memory Working Set Percentage
2507 unit: percentage
2508 chart_type: line
2509 dimensions:
2510 - name: average
2511 - name: maximum
2512 - name: azure_monitor.aks.node_memory_rss
2513 description: AKS Node Memory RSS
2514 unit: bytes
2515 chart_type: line
2516 dimensions:
2517 - name: average
2518 - name: maximum
2519 - name: azure_monitor.aks.node_memory_rss_percentage
2520 description: AKS Node Memory RSS Percentage
2521 unit: percentage
2522 chart_type: line
2523 dimensions:
2524 - name: average
2525 - name: maximum
2526 - name: azure_monitor.aks.node_disk_usage
2527 description: AKS Node Disk Usage
2528 unit: bytes
2529 chart_type: line
2530 dimensions:
2531 - name: average
2532 - name: maximum
2533 - name: azure_monitor.aks.node_disk_percentage
2534 description: AKS Node Disk Usage Percentage
2535 unit: percentage
2536 chart_type: line
2537 dimensions:
2538 - name: average
2539 - name: maximum
2540 - name: azure_monitor.aks.node_network
2541 description: AKS Node Network Traffic
2542 unit: bytes
2543 chart_type: line
2544 dimensions:
2545 - name: in
2546 - name: out
2547 - <<: *module
2548 meta:
2549 <<: *meta
2550 id: collector-go.d.plugin-azure_monitor-storage_accounts
2551 monitored_instance:
2552 name: Azure Storage Account
2553 link: https://learn.microsoft.com/azure/storage/common/storage-account-overview
2554 icon_filename: azure.svg
2555 categories:
2556 - data-collection.cloud-and-devops
2557 keywords:
2558 - azure
2559 - storage
2560 - blob
2561 - account
2562 - files
2563 - queue
2564 - table
2565 overview:
2566 <<: *overview
2567 data_collection:
2568 metrics_description: |
2569 :::info
2570
2571 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
2572
2573 :::
2574
2575 Monitor Azure Storage Account with metrics covering:
2576
2577 - **Transactions** -- transaction count
2578 - **Latency** -- end-to-end latency and server latency (average/max)
2579 - **Throughput** -- ingress and egress bytes per second
2580 - **Availability** -- service availability percentage
2581 - **Capacity** -- used storage capacity
2582 method_description: *method_description
2583 alerts:
2584 - name: am_storage_accounts_availability
2585 metric: azure_monitor.storage_accounts.availability
2586 info: "Storage availability on ${label:resource_name}"
2587 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf
2588 - name: am_storage_accounts_e2e_latency
2589 metric: azure_monitor.storage_accounts.e2e_latency
2590 info: "Storage E2E latency on ${label:resource_name}"
2591 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf
2592 - name: am_storage_accounts_e2e_latency_peak
2593 metric: azure_monitor.storage_accounts.e2e_latency
2594 info: "Storage E2E latency peak on ${label:resource_name}"
2595 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf
2596 - name: am_storage_accounts_server_latency
2597 metric: azure_monitor.storage_accounts.server_latency
2598 info: "Storage server latency on ${label:resource_name}"
2599 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf
2600 - name: am_storage_accounts_server_latency_peak
2601 metric: azure_monitor.storage_accounts.server_latency
2602 info: "Storage server latency peak on ${label:resource_name}"
2603 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf
2604 metrics:
2605 folding:
2606 title: Metrics
2607 enabled: false
2608 description: ""
2609 availability: []
2610 scopes:
2611 - name: resource
2612 description: "These metrics refer to each monitored Azure resource."
2613 labels:
2614 - name: resource_name
2615 description: "The Azure resource name."
2616 - name: resource_group
2617 description: "The Azure resource group."
2618 - name: region
2619 description: "The Azure region where the resource is deployed."
2620 - name: resource_type
2621 description: "The Azure resource type identifier."
2622 - name: profile
2623 description: "The Azure Monitor profile basename."
2624 - name: subscription_id
2625 description: "The Azure subscription identifier."
2626 - name: resource_uid
2627 description: "The unique Azure resource identifier."
2628 metrics:
2629 - name: azure_monitor.storage_accounts.availability
2630 description: Azure Storage Account Availability
2631 unit: percentage
2632 chart_type: line
2633 dimensions:
2634 - name: average
2635 - name: azure_monitor.storage_accounts.transactions
2636 description: Azure Storage Account Transactions
2637 unit: transactions/s
2638 chart_type: line
2639 dimensions:
2640 - name: total
2641 - name: azure_monitor.storage_accounts.throughput
2642 description: Azure Storage Account Throughput
2643 unit: bytes/s
2644 chart_type: line
2645 dimensions:
2646 - name: ingress
2647 - name: egress
2648 - name: azure_monitor.storage_accounts.e2e_latency
2649 description: Azure Storage Account End-to-End Latency
2650 unit: milliseconds
2651 chart_type: line
2652 dimensions:
2653 - name: average
2654 - name: maximum
2655 - name: azure_monitor.storage_accounts.server_latency
2656 description: Azure Storage Account Server Latency
2657 unit: milliseconds
2658 chart_type: line
2659 dimensions:
2660 - name: average
2661 - name: maximum
2662 - name: azure_monitor.storage_accounts.used_capacity
2663 description: Azure Storage Account Used Capacity
2664 unit: bytes
2665 chart_type: line
2666 dimensions:
2667 - name: average
2668 - <<: *module
2669 meta:
2670 <<: *meta
2671 id: collector-go.d.plugin-azure_monitor-load_balancers
2672 monitored_instance:
2673 name: Azure Load Balancer
2674 link: https://learn.microsoft.com/azure/load-balancer/
2675 icon_filename: azure.svg
2676 categories:
2677 - data-collection.cloud-and-devops
2678 keywords:
2679 - azure
2680 - load
2681 - balancer
2682 - networking
2683 - lb
2684 overview:
2685 <<: *overview
2686 data_collection:
2687 metrics_description: |
2688 :::info
2689
2690 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
2691
2692 :::
2693
2694 Monitor Azure Load Balancer with metrics covering:
2695
2696 - **Availability** -- data path availability, health probe status, global backend availability
2697 - **Throughput** -- byte and packet throughput
2698 - **Connections** -- SNAT connections, SYN packet count
2699 - **SNAT ports** -- allocated and used SNAT ports
2700 method_description: *method_description
2701 alerts:
2702 - name: am_load_balancers_vip_availability
2703 metric: azure_monitor.load_balancers.vip_availability
2704 info: "LB data path availability on ${label:resource_name}"
2705 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf
2706 - name: am_load_balancers_dip_availability
2707 metric: azure_monitor.load_balancers.dip_availability
2708 info: "LB health probe status on ${label:resource_name}"
2709 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf
2710 - name: am_load_balancers_global_backend_availability
2711 metric: azure_monitor.load_balancers.global_backend_availability
2712 info: "LB global backend availability on ${label:resource_name}"
2713 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf
2714 - name: am_load_balancers_snat_port_utilization
2715 metric: azure_monitor.load_balancers.snat_ports
2716 info: "LB SNAT port utilization on ${label:resource_name}"
2717 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf
2718 metrics:
2719 folding:
2720 title: Metrics
2721 enabled: false
2722 description: ""
2723 availability: []
2724 scopes:
2725 - name: resource
2726 description: "These metrics refer to each monitored Azure resource."
2727 labels:
2728 - name: resource_name
2729 description: "The Azure resource name."
2730 - name: resource_group
2731 description: "The Azure resource group."
2732 - name: region
2733 description: "The Azure region where the resource is deployed."
2734 - name: resource_type
2735 description: "The Azure resource type identifier."
2736 - name: profile
2737 description: "The Azure Monitor profile basename."
2738 - name: subscription_id
2739 description: "The Azure subscription identifier."
2740 - name: resource_uid
2741 description: "The unique Azure resource identifier."
2742 metrics:
2743 - name: azure_monitor.load_balancers.vip_availability
2744 description: Azure Load Balancer Data Path Availability
2745 unit: percentage
2746 chart_type: line
2747 dimensions:
2748 - name: average
2749 - name: azure_monitor.load_balancers.dip_availability
2750 description: Azure Load Balancer Health Probe Status
2751 unit: percentage
2752 chart_type: line
2753 dimensions:
2754 - name: average
2755 - name: azure_monitor.load_balancers.global_backend_availability
2756 description: Azure Load Balancer Global Backend Availability
2757 unit: percentage
2758 chart_type: line
2759 dimensions:
2760 - name: average
2761 - name: azure_monitor.load_balancers.byte_throughput
2762 description: Azure Load Balancer Byte Throughput
2763 unit: bytes/s
2764 chart_type: line
2765 dimensions:
2766 - name: total
2767 - name: azure_monitor.load_balancers.packet_throughput
2768 description: Azure Load Balancer Packet Throughput
2769 unit: packets/s
2770 chart_type: line
2771 dimensions:
2772 - name: total
2773 - name: azure_monitor.load_balancers.syn_count
2774 description: Azure Load Balancer SYN Packets
2775 unit: packets/s
2776 chart_type: line
2777 dimensions:
2778 - name: total
2779 - name: azure_monitor.load_balancers.snat_connections
2780 description: Azure Load Balancer SNAT Connections
2781 unit: connections/s
2782 chart_type: line
2783 dimensions:
2784 - name: total
2785 - name: azure_monitor.load_balancers.snat_ports
2786 description: Azure Load Balancer SNAT Port Usage
2787 unit: ports
2788 chart_type: line
2789 dimensions:
2790 - name: allocated
2791 - name: used
2792 - <<: *module
2793 meta:
2794 <<: *meta
2795 id: collector-go.d.plugin-azure_monitor-app_service
2796 monitored_instance:
2797 name: Azure App Service
2798 link: https://learn.microsoft.com/azure/app-service/
2799 icon_filename: azure.svg
2800 categories:
2801 - data-collection.cloud-and-devops
2802 keywords:
2803 - azure
2804 - app
2805 - service
2806 - web
2807 - webapp
2808 - paas
2809 overview:
2810 <<: *overview
2811 data_collection:
2812 metrics_description: |
2813 :::info
2814
2815 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
2816
2817 :::
2818
2819 Monitor Azure App Service with metrics covering:
2820
2821 - **Requests** -- HTTP request rate, response status codes (2xx/3xx/4xx/5xx), error detail (401/403/404/406)
2822 - **Performance** -- response time, request queue depth
2823 - **Compute** -- CPU utilization, CPU time consumed
2824 - **Memory** -- memory usage (average working set, working set, private bytes)
2825 - **Network** -- network traffic (received/sent), I/O throughput (read/write/other)
2826 - **I/O** -- I/O operations (read/write/other), file handles
2827 - **.NET runtime** -- threads, GC collections (gen0/gen1/gen2), loaded assemblies, app domains
2828 - **Functions** -- function executions and execution units (MB-ms), always-ready and on-demand units
2829 - **Health** -- health check status
2830 method_description: *method_description
2831 alerts:
2832 - name: am_app_service_health_check
2833 metric: azure_monitor.app_service.health
2834 info: "App Service health on ${label:resource_name}"
2835 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf
2836 - name: am_app_service_http_5xx_rate
2837 metric: azure_monitor.app_service.http_status
2838 info: "App Service 5xx errors on ${label:resource_name}"
2839 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf
2840 - name: am_app_service_response_time
2841 metric: azure_monitor.app_service.response_time
2842 info: "App Service response time on ${label:resource_name}"
2843 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf
2844 - name: am_app_service_cpu_utilization
2845 metric: azure_monitor.app_service.cpu
2846 info: "App Service CPU on ${label:resource_name}"
2847 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf
2848 - name: am_app_service_request_queue
2849 metric: azure_monitor.app_service.request_queue
2850 info: "App Service request queue on ${label:resource_name}"
2851 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf
2852 - name: am_app_service_http_4xx_rate
2853 metric: azure_monitor.app_service.http_status
2854 info: "App Service 4xx errors on ${label:resource_name}"
2855 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf
2856 - name: am_app_service_http_403_rate
2857 metric: azure_monitor.app_service.http_error_detail
2858 info: "App Service 403 forbidden on ${label:resource_name}"
2859 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf
2860 - name: am_app_service_http_401_rate
2861 metric: azure_monitor.app_service.http_error_detail
2862 info: "App Service 401 unauthorized on ${label:resource_name}"
2863 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf
2864 metrics:
2865 folding:
2866 title: Metrics
2867 enabled: false
2868 description: ""
2869 availability: []
2870 scopes:
2871 - name: resource
2872 description: "These metrics refer to each monitored Azure resource."
2873 labels:
2874 - name: resource_name
2875 description: "The Azure resource name."
2876 - name: resource_group
2877 description: "The Azure resource group."
2878 - name: region
2879 description: "The Azure region where the resource is deployed."
2880 - name: resource_type
2881 description: "The Azure resource type identifier."
2882 - name: profile
2883 description: "The Azure Monitor profile basename."
2884 - name: subscription_id
2885 description: "The Azure subscription identifier."
2886 - name: resource_uid
2887 description: "The unique Azure resource identifier."
2888 metrics:
2889 - name: azure_monitor.app_service.requests
2890 description: Azure App Service Requests
2891 unit: requests/s
2892 chart_type: line
2893 dimensions:
2894 - name: requests
2895 - name: azure_monitor.app_service.response_time
2896 description: Azure App Service Response Time
2897 unit: seconds
2898 chart_type: line
2899 dimensions:
2900 - name: average
2901 - name: azure_monitor.app_service.http_status
2902 description: Azure App Service HTTP Status Codes
2903 unit: responses/s
2904 chart_type: line
2905 dimensions:
2906 - name: 2xx
2907 - name: 3xx
2908 - name: 4xx
2909 - name: 5xx
2910 - name: azure_monitor.app_service.http_error_detail
2911 description: Azure App Service HTTP Error Detail
2912 unit: responses/s
2913 chart_type: line
2914 dimensions:
2915 - name: 101_websocket
2916 - name: 401_unauthorized
2917 - name: 403_forbidden
2918 - name: 404_not_found
2919 - name: 406_not_acceptable
2920 - name: azure_monitor.app_service.cpu
2921 description: Azure App Service CPU Utilization
2922 unit: percentage
2923 chart_type: line
2924 dimensions:
2925 - name: average
2926 - name: azure_monitor.app_service.cpu_time
2927 description: Azure App Service CPU Time
2928 unit: seconds
2929 chart_type: line
2930 dimensions:
2931 - name: total
2932 - name: azure_monitor.app_service.memory_usage
2933 description: Azure App Service Memory Usage
2934 unit: bytes
2935 chart_type: line
2936 dimensions:
2937 - name: average_working_set
2938 - name: working_set
2939 - name: private
2940 - name: azure_monitor.app_service.health
2941 description: Azure App Service Health Check Status
2942 unit: percentage
2943 chart_type: line
2944 dimensions:
2945 - name: average
2946 - name: azure_monitor.app_service.network_traffic
2947 description: Azure App Service Network Traffic
2948 unit: bytes/s
2949 chart_type: line
2950 dimensions:
2951 - name: received
2952 - name: sent
2953 - name: azure_monitor.app_service.connections
2954 description: Azure App Service Connections
2955 unit: connections
2956 chart_type: line
2957 dimensions:
2958 - name: average
2959 - name: azure_monitor.app_service.io_throughput
2960 description: Azure App Service IO Throughput
2961 unit: bytes/s
2962 chart_type: line
2963 dimensions:
2964 - name: read
2965 - name: write
2966 - name: other
2967 - name: azure_monitor.app_service.io_operations
2968 description: Azure App Service IO Operations
2969 unit: operations/s
2970 chart_type: line
2971 dimensions:
2972 - name: read
2973 - name: write
2974 - name: other
2975 - name: azure_monitor.app_service.threads
2976 description: Azure App Service Threads
2977 unit: threads
2978 chart_type: line
2979 dimensions:
2980 - name: average
2981 - name: azure_monitor.app_service.handles
2982 description: Azure App Service Handles
2983 unit: handles
2984 chart_type: line
2985 dimensions:
2986 - name: average
2987 - name: azure_monitor.app_service.gc_collections
2988 description: Azure App Service .NET GC Collections
2989 unit: collections/s
2990 chart_type: line
2991 dimensions:
2992 - name: gen0
2993 - name: gen1
2994 - name: gen2
2995 - name: azure_monitor.app_service.function_executions
2996 description: Azure App Service Function Executions
2997 unit: executions/s
2998 chart_type: line
2999 dimensions:
3000 - name: total
3001 - name: azure_monitor.app_service.function_execution_units
3002 description: Azure App Service Function Execution Units
3003 unit: MB-milliseconds/s
3004 chart_type: line
3005 dimensions:
3006 - name: total
3007 - name: azure_monitor.app_service.always_ready_function_executions
3008 description: Azure App Service Always Ready Function Executions
3009 unit: executions/s
3010 chart_type: line
3011 dimensions:
3012 - name: total
3013 - name: azure_monitor.app_service.always_ready_function_execution_units
3014 description: Azure App Service Always Ready Function Execution Units
3015 unit: MB-milliseconds/s
3016 chart_type: line
3017 dimensions:
3018 - name: total
3019 - name: azure_monitor.app_service.always_ready_units
3020 description: Azure App Service Always Ready Units
3021 unit: units
3022 chart_type: line
3023 dimensions:
3024 - name: total
3025 - name: azure_monitor.app_service.on_demand_function_executions
3026 description: Azure App Service On Demand Function Executions
3027 unit: executions/s
3028 chart_type: line
3029 dimensions:
3030 - name: total
3031 - name: azure_monitor.app_service.on_demand_function_execution_units
3032 description: Azure App Service On Demand Function Execution Units
3033 unit: MB-milliseconds/s
3034 chart_type: line
3035 dimensions:
3036 - name: total
3037 - name: azure_monitor.app_service.request_queue
3038 description: Azure App Service Request Queue
3039 unit: requests
3040 chart_type: line
3041 dimensions:
3042 - name: queued
3043 - name: azure_monitor.app_service.instances
3044 description: Azure App Service Instance Count
3045 unit: instances
3046 chart_type: line
3047 dimensions:
3048 - name: running
3049 - name: azure_monitor.app_service.assemblies
3050 description: Azure App Service .NET Assemblies
3051 unit: assemblies
3052 chart_type: line
3053 dimensions:
3054 - name: loaded
3055 - name: azure_monitor.app_service.app_domains
3056 description: Azure App Service App Domains
3057 unit: domains
3058 chart_type: line
3059 dimensions:
3060 - name: loaded
3061 - name: unloaded
3062 - <<: *module
3063 meta:
3064 <<: *meta
3065 id: collector-go.d.plugin-azure_monitor-azure_functions
3066 monitored_instance:
3067 name: Azure Functions
3068 link: https://learn.microsoft.com/azure/azure-functions/
3069 icon_filename: azure.svg
3070 categories:
3071 - data-collection.cloud-and-devops
3072 keywords:
3073 - azure
3074 - functions
3075 - serverless
3076 - faas
3077 - lambda
3078 overview:
3079 <<: *overview
3080 data_collection:
3081 metrics_description: |
3082 :::info
3083
3084 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
3085
3086 :::
3087
3088 Monitor Azure Functions with metrics covering:
3089
3090 - **Executions** -- function invocation counts, execution units (MB-milliseconds)
3091 - **HTTP** -- request rates, response status codes
3092 - **Compute** -- CPU utilization, CPU time consumed
3093 - **Memory** -- memory usage (working set, private bytes)
3094 - **Flex Consumption** -- always-ready and on-demand function executions and units
3095
3096 Azure Functions runs on the App Service platform and shares the same underlying metrics.
3097 method_description: *method_description
3098 metrics:
3099 folding:
3100 title: Metrics
3101 enabled: false
3102 description: ""
3103 availability: []
3104 scopes:
3105 - name: resource
3106 description: "These metrics refer to each monitored Azure resource."
3107 labels:
3108 - name: resource_name
3109 description: "The Azure resource name."
3110 - name: resource_group
3111 description: "The Azure resource group."
3112 - name: region
3113 description: "The Azure region where the resource is deployed."
3114 - name: resource_type
3115 description: "The Azure resource type identifier."
3116 - name: profile
3117 description: "The Azure Monitor profile basename."
3118 - name: subscription_id
3119 description: "The Azure subscription identifier."
3120 - name: resource_uid
3121 description: "The unique Azure resource identifier."
3122 metrics:
3123 - name: azure_monitor.app_service.requests
3124 description: Azure App Service Requests
3125 unit: requests/s
3126 chart_type: line
3127 dimensions:
3128 - name: requests
3129 - name: azure_monitor.app_service.response_time
3130 description: Azure App Service Response Time
3131 unit: seconds
3132 chart_type: line
3133 dimensions:
3134 - name: average
3135 - name: azure_monitor.app_service.http_status
3136 description: Azure App Service HTTP Status Codes
3137 unit: responses/s
3138 chart_type: line
3139 dimensions:
3140 - name: 2xx
3141 - name: 3xx
3142 - name: 4xx
3143 - name: 5xx
3144 - name: azure_monitor.app_service.http_error_detail
3145 description: Azure App Service HTTP Error Detail
3146 unit: responses/s
3147 chart_type: line
3148 dimensions:
3149 - name: 101_websocket
3150 - name: 401_unauthorized
3151 - name: 403_forbidden
3152 - name: 404_not_found
3153 - name: 406_not_acceptable
3154 - name: azure_monitor.app_service.cpu
3155 description: Azure App Service CPU Utilization
3156 unit: percentage
3157 chart_type: line
3158 dimensions:
3159 - name: average
3160 - name: azure_monitor.app_service.cpu_time
3161 description: Azure App Service CPU Time
3162 unit: seconds
3163 chart_type: line
3164 dimensions:
3165 - name: total
3166 - name: azure_monitor.app_service.memory_usage
3167 description: Azure App Service Memory Usage
3168 unit: bytes
3169 chart_type: line
3170 dimensions:
3171 - name: average_working_set
3172 - name: working_set
3173 - name: private
3174 - name: azure_monitor.app_service.health
3175 description: Azure App Service Health Check Status
3176 unit: percentage
3177 chart_type: line
3178 dimensions:
3179 - name: average
3180 - name: azure_monitor.app_service.network_traffic
3181 description: Azure App Service Network Traffic
3182 unit: bytes/s
3183 chart_type: line
3184 dimensions:
3185 - name: received
3186 - name: sent
3187 - name: azure_monitor.app_service.connections
3188 description: Azure App Service Connections
3189 unit: connections
3190 chart_type: line
3191 dimensions:
3192 - name: average
3193 - name: azure_monitor.app_service.io_throughput
3194 description: Azure App Service IO Throughput
3195 unit: bytes/s
3196 chart_type: line
3197 dimensions:
3198 - name: read
3199 - name: write
3200 - name: other
3201 - name: azure_monitor.app_service.io_operations
3202 description: Azure App Service IO Operations
3203 unit: operations/s
3204 chart_type: line
3205 dimensions:
3206 - name: read
3207 - name: write
3208 - name: other
3209 - name: azure_monitor.app_service.threads
3210 description: Azure App Service Threads
3211 unit: threads
3212 chart_type: line
3213 dimensions:
3214 - name: average
3215 - name: azure_monitor.app_service.handles
3216 description: Azure App Service Handles
3217 unit: handles
3218 chart_type: line
3219 dimensions:
3220 - name: average
3221 - name: azure_monitor.app_service.gc_collections
3222 description: Azure App Service .NET GC Collections
3223 unit: collections/s
3224 chart_type: line
3225 dimensions:
3226 - name: gen0
3227 - name: gen1
3228 - name: gen2
3229 - name: azure_monitor.app_service.function_executions
3230 description: Azure App Service Function Executions
3231 unit: executions/s
3232 chart_type: line
3233 dimensions:
3234 - name: total
3235 - name: azure_monitor.app_service.function_execution_units
3236 description: Azure App Service Function Execution Units
3237 unit: MB-milliseconds/s
3238 chart_type: line
3239 dimensions:
3240 - name: total
3241 - name: azure_monitor.app_service.always_ready_function_executions
3242 description: Azure App Service Always Ready Function Executions
3243 unit: executions/s
3244 chart_type: line
3245 dimensions:
3246 - name: total
3247 - name: azure_monitor.app_service.always_ready_function_execution_units
3248 description: Azure App Service Always Ready Function Execution Units
3249 unit: MB-milliseconds/s
3250 chart_type: line
3251 dimensions:
3252 - name: total
3253 - name: azure_monitor.app_service.always_ready_units
3254 description: Azure App Service Always Ready Units
3255 unit: units
3256 chart_type: line
3257 dimensions:
3258 - name: total
3259 - name: azure_monitor.app_service.on_demand_function_executions
3260 description: Azure App Service On Demand Function Executions
3261 unit: executions/s
3262 chart_type: line
3263 dimensions:
3264 - name: total
3265 - name: azure_monitor.app_service.on_demand_function_execution_units
3266 description: Azure App Service On Demand Function Execution Units
3267 unit: MB-milliseconds/s
3268 chart_type: line
3269 dimensions:
3270 - name: total
3271 - name: azure_monitor.app_service.request_queue
3272 description: Azure App Service Request Queue
3273 unit: requests
3274 chart_type: line
3275 dimensions:
3276 - name: queued
3277 - name: azure_monitor.app_service.instances
3278 description: Azure App Service Instance Count
3279 unit: instances
3280 chart_type: line
3281 dimensions:
3282 - name: running
3283 - name: azure_monitor.app_service.assemblies
3284 description: Azure App Service .NET Assemblies
3285 unit: assemblies
3286 chart_type: line
3287 dimensions:
3288 - name: loaded
3289 - name: azure_monitor.app_service.app_domains
3290 description: Azure App Service App Domains
3291 unit: domains
3292 chart_type: line
3293 dimensions:
3294 - name: loaded
3295 - name: unloaded
3296 - <<: *module
3297 meta:
3298 <<: *meta
3299 id: collector-go.d.plugin-azure_monitor-redis_cache
3300 monitored_instance:
3301 name: Azure Cache for Redis
3302 link: https://learn.microsoft.com/azure/azure-cache-for-redis/
3303 icon_filename: azure.svg
3304 categories:
3305 - data-collection.cloud-and-devops
3306 keywords:
3307 - azure
3308 - redis
3309 - cache
3310 - memory
3311 - nosql
3312 overview:
3313 <<: *overview
3314 data_collection:
3315 metrics_description: |
3316 :::info
3317
3318 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
3319
3320 :::
3321
3322 Monitor Azure Cache for Redis with metrics covering:
3323
3324 - **Performance** -- operations/second, command processing rates (get/set), cache hit/miss rates
3325 - **Latency** -- average latency, P99 latency
3326 - **Compute** -- CPU utilization, server load
3327 - **Memory** -- memory usage (used/RSS), memory utilization
3328 - **Connections** -- connected clients, connection rate (created/closed)
3329 - **Keys** -- total keys, evicted keys, expired keys, miss rate
3330 - **Throughput** -- read/write bytes per second
3331 - **Geo-replication** -- replication health, connectivity lag, sync events, data sync offset
3332 - **Per-shard** -- instance-level breakdowns for hit rate, clients, commands, server load, keys, operations, throughput
3333 method_description: *method_description
3334 alerts:
3335 - name: am_redis_cache_server_load
3336 metric: azure_monitor.redis_cache.server_load
3337 info: "Redis server load on ${label:resource_name}"
3338 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3339 - name: am_redis_cache_cpu
3340 metric: azure_monitor.redis_cache.cpu
3341 info: "Redis CPU on ${label:resource_name}"
3342 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3343 - name: am_redis_cache_memory_utilization
3344 metric: azure_monitor.redis_cache.memory_utilization
3345 info: "Redis memory utilization on ${label:resource_name}"
3346 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3347 - name: am_redis_cache_miss_rate
3348 metric: azure_monitor.redis_cache.miss_rate
3349 info: "Redis cache miss rate on ${label:resource_name}"
3350 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3351 - name: am_redis_cache_errors
3352 metric: azure_monitor.redis_cache.errors
3353 info: "Redis errors on ${label:resource_name}"
3354 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3355 - name: am_redis_cache_latency
3356 metric: azure_monitor.redis_cache.latency
3357 info: "Redis average latency on ${label:resource_name}"
3358 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3359 - name: am_redis_cache_latency_p99
3360 metric: azure_monitor.redis_cache.latency_p99
3361 info: "Redis P99 latency on ${label:resource_name}"
3362 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3363 - name: am_redis_cache_evicted_keys
3364 metric: azure_monitor.redis_cache.key_events
3365 info: "Redis key evictions on ${label:resource_name}"
3366 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3367 - name: am_redis_cache_geo_replication_health
3368 metric: azure_monitor.redis_cache.geo_replication_health
3369 info: "Redis geo-replication health on ${label:resource_name}"
3370 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3371 - name: am_redis_cache_geo_replication_lag
3372 metric: azure_monitor.redis_cache.geo_replication_lag
3373 info: "Redis geo-replication lag on ${label:resource_name}"
3374 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3375 - name: am_redis_cache_geo_replication_sync_offset
3376 metric: azure_monitor.redis_cache.geo_replication_sync_offset
3377 info: "Redis geo-replication sync offset on ${label:resource_name}"
3378 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf
3379 metrics:
3380 folding:
3381 title: Metrics
3382 enabled: false
3383 description: ""
3384 availability: []
3385 scopes:
3386 - name: resource
3387 description: "These metrics refer to each monitored Azure resource."
3388 labels:
3389 - name: resource_name
3390 description: "The Azure resource name."
3391 - name: resource_group
3392 description: "The Azure resource group."
3393 - name: region
3394 description: "The Azure region where the resource is deployed."
3395 - name: resource_type
3396 description: "The Azure resource type identifier."
3397 - name: profile
3398 description: "The Azure Monitor profile basename."
3399 - name: subscription_id
3400 description: "The Azure subscription identifier."
3401 - name: resource_uid
3402 description: "The unique Azure resource identifier."
3403 metrics:
3404 - name: azure_monitor.redis_cache.cache_hits
3405 description: Azure Cache for Redis Hit Rate
3406 unit: operations/s
3407 chart_type: line
3408 dimensions:
3409 - name: hits
3410 - name: misses
3411 - name: azure_monitor.redis_cache.throughput
3412 description: Azure Cache for Redis Throughput
3413 unit: bytes/s
3414 chart_type: line
3415 dimensions:
3416 - name: read
3417 - name: write
3418 - name: azure_monitor.redis_cache.server_load
3419 description: Azure Cache for Redis Server Load
3420 unit: percentage
3421 chart_type: line
3422 dimensions:
3423 - name: maximum
3424 - name: azure_monitor.redis_cache.cpu
3425 description: Azure Cache for Redis CPU Utilization
3426 unit: percentage
3427 chart_type: line
3428 dimensions:
3429 - name: maximum
3430 - name: azure_monitor.redis_cache.memory_usage
3431 description: Azure Cache for Redis Memory Usage
3432 unit: bytes
3433 chart_type: line
3434 dimensions:
3435 - name: used
3436 - name: rss
3437 - name: azure_monitor.redis_cache.memory_utilization
3438 description: Azure Cache for Redis Memory Utilization
3439 unit: percentage
3440 chart_type: line
3441 dimensions:
3442 - name: maximum
3443 - name: azure_monitor.redis_cache.clients
3444 description: Azure Cache for Redis Connected Clients
3445 unit: clients
3446 chart_type: line
3447 dimensions:
3448 - name: maximum
3449 - name: azure_monitor.redis_cache.operations
3450 description: Azure Cache for Redis Operations
3451 unit: operations/s
3452 chart_type: line
3453 dimensions:
3454 - name: maximum
3455 - name: azure_monitor.redis_cache.commands
3456 description: Azure Cache for Redis Commands Processed
3457 unit: commands/s
3458 chart_type: line
3459 dimensions:
3460 - name: total
3461 - name: azure_monitor.redis_cache.command_types
3462 description: Azure Cache for Redis Command Types
3463 unit: commands/s
3464 chart_type: line
3465 dimensions:
3466 - name: get
3467 - name: set
3468 - name: azure_monitor.redis_cache.latency
3469 description: Azure Cache for Redis Latency
3470 unit: microseconds
3471 chart_type: line
3472 dimensions:
3473 - name: average
3474 - name: azure_monitor.redis_cache.key_events
3475 description: Azure Cache for Redis Key Events
3476 unit: keys/s
3477 chart_type: line
3478 dimensions:
3479 - name: evicted
3480 - name: expired
3481 - name: azure_monitor.redis_cache.total_keys
3482 description: Azure Cache for Redis Total Keys
3483 unit: keys
3484 chart_type: line
3485 dimensions:
3486 - name: maximum
3487 - name: azure_monitor.redis_cache.errors
3488 description: Azure Cache for Redis Errors
3489 unit: errors
3490 chart_type: line
3491 dimensions:
3492 - name: maximum
3493 - name: azure_monitor.redis_cache.miss_rate
3494 description: Azure Cache for Redis Miss Rate
3495 unit: percentage
3496 chart_type: line
3497 dimensions:
3498 - name: miss_rate
3499 - name: azure_monitor.redis_cache.latency_p99
3500 description: Azure Cache for Redis P99 Latency
3501 unit: microseconds
3502 chart_type: line
3503 dimensions:
3504 - name: p99
3505 - name: azure_monitor.redis_cache.connection_rate
3506 description: Azure Cache for Redis Connection Rate
3507 unit: connections/s
3508 chart_type: line
3509 dimensions:
3510 - name: created
3511 - name: closed
3512 - name: azure_monitor.redis_cache.aad_clients
3513 description: Azure Cache for Redis Entra Token Clients
3514 unit: clients
3515 chart_type: line
3516 dimensions:
3517 - name: maximum
3518 - name: azure_monitor.redis_cache.instance_cache_hits
3519 description: Azure Cache for Redis Instance Hit Rate
3520 unit: operations/s
3521 chart_type: line
3522 dimensions:
3523 - name: hits
3524 - name: misses
3525 - name: azure_monitor.redis_cache.instance_throughput
3526 description: Azure Cache for Redis Instance Throughput
3527 unit: bytes/s
3528 chart_type: line
3529 dimensions:
3530 - name: read
3531 - name: write
3532 - name: azure_monitor.redis_cache.instance_server_load
3533 description: Azure Cache for Redis Instance Server Load
3534 unit: percentage
3535 chart_type: line
3536 dimensions:
3537 - name: server_load
3538 - name: cpu
3539 - name: azure_monitor.redis_cache.instance_memory_usage
3540 description: Azure Cache for Redis Instance Memory Usage
3541 unit: bytes
3542 chart_type: line
3543 dimensions:
3544 - name: used
3545 - name: rss
3546 - name: azure_monitor.redis_cache.instance_memory_utilization
3547 description: Azure Cache for Redis Instance Memory Utilization
3548 unit: percentage
3549 chart_type: line
3550 dimensions:
3551 - name: maximum
3552 - name: azure_monitor.redis_cache.instance_clients
3553 description: Azure Cache for Redis Instance Connected Clients
3554 unit: clients
3555 chart_type: line
3556 dimensions:
3557 - name: maximum
3558 - name: azure_monitor.redis_cache.instance_operations
3559 description: Azure Cache for Redis Instance Operations
3560 unit: operations/s
3561 chart_type: line
3562 dimensions:
3563 - name: maximum
3564 - name: azure_monitor.redis_cache.instance_commands
3565 description: Azure Cache for Redis Instance Commands Processed
3566 unit: commands/s
3567 chart_type: line
3568 dimensions:
3569 - name: total
3570 - name: get
3571 - name: set
3572 - name: azure_monitor.redis_cache.instance_total_keys
3573 description: Azure Cache for Redis Instance Total Keys
3574 unit: keys
3575 chart_type: line
3576 dimensions:
3577 - name: maximum
3578 - name: azure_monitor.redis_cache.instance_key_events
3579 description: Azure Cache for Redis Instance Key Events
3580 unit: keys/s
3581 chart_type: line
3582 dimensions:
3583 - name: evicted
3584 - name: expired
3585 - name: azure_monitor.redis_cache.geo_replication_lag
3586 description: Azure Cache for Redis Geo-Replication Connectivity Lag
3587 unit: seconds
3588 chart_type: line
3589 dimensions:
3590 - name: average
3591 - name: azure_monitor.redis_cache.geo_replication_sync_offset
3592 description: Azure Cache for Redis Geo-Replication Data Sync Offset
3593 unit: bytes
3594 chart_type: line
3595 dimensions:
3596 - name: average
3597 - name: azure_monitor.redis_cache.geo_replication_sync_events
3598 description: Azure Cache for Redis Geo-Replication Sync Events
3599 unit: events/s
3600 chart_type: line
3601 dimensions:
3602 - name: started
3603 - name: finished
3604 - name: azure_monitor.redis_cache.geo_replication_health
3605 description: Azure Cache for Redis Geo-Replication Health
3606 unit: status
3607 chart_type: line
3608 dimensions:
3609 - name: average
3610 - <<: *module
3611 meta:
3612 <<: *meta
3613 id: collector-go.d.plugin-azure_monitor-event_hubs
3614 monitored_instance:
3615 name: Azure Event Hubs Namespace
3616 link: https://learn.microsoft.com/azure/event-hubs/
3617 icon_filename: azure.svg
3618 categories:
3619 - data-collection.cloud-and-devops
3620 keywords:
3621 - azure
3622 - event
3623 - hubs
3624 - streaming
3625 - kafka
3626 - messaging
3627 overview:
3628 <<: *overview
3629 data_collection:
3630 metrics_description: |
3631 :::info
3632
3633 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
3634
3635 :::
3636
3637 Monitor Azure Event Hubs with metrics covering:
3638
3639 - **Messages** -- message flow (in/out), captured messages and bytes
3640 - **Throughput** -- data throughput (in/out bytes per second)
3641 - **Connections** -- active connections, connection events (opened/closed)
3642 - **Requests** -- incoming and successful request rates
3643 - **Errors** -- server errors, user errors, throttled requests, quota exceeded
3644 - **Replication** -- replication lag (messages and duration)
3645 - **Resources** -- namespace size, CPU and memory utilization
3646 method_description: *method_description
3647 alerts:
3648 - name: am_event_hubs_server_errors
3649 metric: azure_monitor.event_hubs.errors
3650 info: "Event Hubs server errors on ${label:resource_name}"
3651 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3652 - name: am_event_hubs_throttled_requests
3653 metric: azure_monitor.event_hubs.errors
3654 info: "Event Hubs throttled requests on ${label:resource_name}"
3655 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3656 - name: am_event_hubs_quota_exceeded
3657 metric: azure_monitor.event_hubs.errors
3658 info: "Event Hubs quota exceeded on ${label:resource_name}"
3659 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3660 - name: am_event_hubs_user_errors
3661 metric: azure_monitor.event_hubs.errors
3662 info: "Event Hubs user errors on ${label:resource_name}"
3663 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3664 - name: am_event_hubs_success_rate
3665 metric: azure_monitor.event_hubs.requests
3666 info: "Event Hubs request success rate on ${label:resource_name}"
3667 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3668 - name: am_event_hubs_namespace_cpu
3669 metric: azure_monitor.event_hubs.namespace_resources
3670 info: "Event Hubs namespace CPU on ${label:resource_name}"
3671 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3672 - name: am_event_hubs_namespace_memory
3673 metric: azure_monitor.event_hubs.namespace_resources
3674 info: "Event Hubs namespace memory on ${label:resource_name}"
3675 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3676 - name: am_event_hubs_capture_backlog
3677 metric: azure_monitor.event_hubs.capture_backlog
3678 info: "Event Hubs capture backlog on ${label:resource_name}"
3679 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3680 - name: am_event_hubs_replication_lag
3681 metric: azure_monitor.event_hubs.replication_lag
3682 info: "Event Hubs replication lag on ${label:resource_name}"
3683 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3684 - name: am_event_hubs_replication_lag_duration
3685 metric: azure_monitor.event_hubs.replication_lag_duration
3686 info: "Event Hubs replication lag duration on ${label:resource_name}"
3687 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf
3688 metrics:
3689 folding:
3690 title: Metrics
3691 enabled: false
3692 description: ""
3693 availability: []
3694 scopes:
3695 - name: resource
3696 description: "These metrics refer to each monitored Azure resource."
3697 labels:
3698 - name: resource_name
3699 description: "The Azure resource name."
3700 - name: resource_group
3701 description: "The Azure resource group."
3702 - name: region
3703 description: "The Azure region where the resource is deployed."
3704 - name: resource_type
3705 description: "The Azure resource type identifier."
3706 - name: profile
3707 description: "The Azure Monitor profile basename."
3708 - name: subscription_id
3709 description: "The Azure subscription identifier."
3710 - name: resource_uid
3711 description: "The unique Azure resource identifier."
3712 metrics:
3713 - name: azure_monitor.event_hubs.message_flow
3714 description: Azure Event Hubs Message Flow
3715 unit: messages/s
3716 chart_type: line
3717 dimensions:
3718 - name: in
3719 - name: out
3720 - name: azure_monitor.event_hubs.data_throughput
3721 description: Azure Event Hubs Data Throughput
3722 unit: bytes/s
3723 chart_type: line
3724 dimensions:
3725 - name: in
3726 - name: out
3727 - name: azure_monitor.event_hubs.requests
3728 description: Azure Event Hubs Requests
3729 unit: requests/s
3730 chart_type: line
3731 dimensions:
3732 - name: incoming
3733 - name: successful
3734 - name: azure_monitor.event_hubs.errors
3735 description: Azure Event Hubs Errors
3736 unit: errors/s
3737 chart_type: line
3738 dimensions:
3739 - name: server
3740 - name: user
3741 - name: throttled
3742 - name: quota_exceeded
3743 - name: azure_monitor.event_hubs.connections
3744 description: Azure Event Hubs Active Connections
3745 unit: connections
3746 chart_type: line
3747 dimensions:
3748 - name: active
3749 - name: azure_monitor.event_hubs.connection_events
3750 description: Azure Event Hubs Connection Events
3751 unit: connections
3752 chart_type: line
3753 dimensions:
3754 - name: opened
3755 - name: closed
3756 - name: azure_monitor.event_hubs.captured_messages
3757 description: Azure Event Hubs Captured Messages
3758 unit: messages/s
3759 chart_type: line
3760 dimensions:
3761 - name: total
3762 - name: azure_monitor.event_hubs.captured_data
3763 description: Azure Event Hubs Captured Data
3764 unit: bytes/s
3765 chart_type: line
3766 dimensions:
3767 - name: total
3768 - name: azure_monitor.event_hubs.namespace_size
3769 description: Azure Event Hubs Namespace Size
3770 unit: bytes
3771 chart_type: line
3772 dimensions:
3773 - name: average
3774 - name: azure_monitor.event_hubs.capture_backlog
3775 description: Azure Event Hubs Capture Backlog
3776 unit: messages
3777 chart_type: line
3778 dimensions:
3779 - name: backlog
3780 - name: azure_monitor.event_hubs.namespace_resources
3781 description: Azure Event Hubs Namespace Resources
3782 unit: percentage
3783 chart_type: line
3784 dimensions:
3785 - name: cpu
3786 - name: memory
3787 - name: azure_monitor.event_hubs.replication_lag
3788 description: Azure Event Hubs Replication Lag
3789 unit: messages
3790 chart_type: line
3791 dimensions:
3792 - name: messages
3793 - name: azure_monitor.event_hubs.replication_lag_duration
3794 description: Azure Event Hubs Replication Lag Duration
3795 unit: seconds
3796 chart_type: line
3797 dimensions:
3798 - name: duration
3799 - <<: *module
3800 meta:
3801 <<: *meta
3802 id: collector-go.d.plugin-azure_monitor-service_bus
3803 monitored_instance:
3804 name: Azure Service Bus Namespace
3805 link: https://learn.microsoft.com/azure/service-bus-messaging/
3806 icon_filename: azure.svg
3807 categories:
3808 - data-collection.cloud-and-devops
3809 keywords:
3810 - azure
3811 - service
3812 - bus
3813 - messaging
3814 - queue
3815 - topic
3816 overview:
3817 <<: *overview
3818 data_collection:
3819 metrics_description: |
3820 :::info
3821
3822 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
3823
3824 :::
3825
3826 Monitor Azure Service Bus with metrics covering:
3827
3828 - **Messages** -- message flow (in/out), active messages, dead-lettered messages, scheduled messages, queue depth
3829 - **Throughput** -- data throughput (in/out bytes per second)
3830 - **Operations** -- completed and abandoned message operations, send latency
3831 - **Connections** -- active connections, connection events (opened/closed)
3832 - **Requests** -- incoming and successful request rates
3833 - **Errors** -- server errors, user errors, throttled requests
3834 - **Replication** -- replication lag (messages and duration)
3835 - **Resources** -- namespace size, CPU and memory utilization, pending checkpoint operations
3836 method_description: *method_description
3837 alerts:
3838 - name: am_service_bus_server_errors
3839 metric: azure_monitor.service_bus.errors
3840 info: "Service Bus server errors on ${label:resource_name}"
3841 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3842 - name: am_service_bus_throttled_requests
3843 metric: azure_monitor.service_bus.errors
3844 info: "Service Bus throttled requests on ${label:resource_name}"
3845 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3846 - name: am_service_bus_user_errors
3847 metric: azure_monitor.service_bus.errors
3848 info: "Service Bus user errors on ${label:resource_name}"
3849 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3850 - name: am_service_bus_namespace_cpu
3851 metric: azure_monitor.service_bus.namespace_resources
3852 info: "Service Bus namespace CPU on ${label:resource_name}"
3853 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3854 - name: am_service_bus_namespace_memory
3855 metric: azure_monitor.service_bus.namespace_resources
3856 info: "Service Bus namespace memory on ${label:resource_name}"
3857 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3858 - name: am_service_bus_send_latency
3859 metric: azure_monitor.service_bus.send_latency
3860 info: "Service Bus send latency on ${label:resource_name}"
3861 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3862 - name: am_service_bus_dead_lettered_messages
3863 metric: azure_monitor.service_bus.problem_messages
3864 info: "Service Bus dead-lettered messages on ${label:resource_name}"
3865 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3866 - name: am_service_bus_active_messages
3867 metric: azure_monitor.service_bus.queue_depth
3868 info: "Service Bus queue depth on ${label:resource_name}"
3869 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3870 - name: am_service_bus_request_success_rate
3871 metric: azure_monitor.service_bus.requests
3872 info: "Service Bus request success rate on ${label:resource_name}"
3873 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3874 - name: am_service_bus_abandoned_messages
3875 metric: azure_monitor.service_bus.message_operations
3876 info: "Service Bus abandoned messages on ${label:resource_name}"
3877 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3878 - name: am_service_bus_replication_lag
3879 metric: azure_monitor.service_bus.replication_lag
3880 info: "Service Bus replication lag on ${label:resource_name}"
3881 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3882 - name: am_service_bus_replication_lag_duration
3883 metric: azure_monitor.service_bus.replication_lag_duration
3884 info: "Service Bus replication lag duration on ${label:resource_name}"
3885 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf
3886 metrics:
3887 folding:
3888 title: Metrics
3889 enabled: false
3890 description: ""
3891 availability: []
3892 scopes:
3893 - name: resource
3894 description: "These metrics refer to each monitored Azure resource."
3895 labels:
3896 - name: resource_name
3897 description: "The Azure resource name."
3898 - name: resource_group
3899 description: "The Azure resource group."
3900 - name: region
3901 description: "The Azure region where the resource is deployed."
3902 - name: resource_type
3903 description: "The Azure resource type identifier."
3904 - name: profile
3905 description: "The Azure Monitor profile basename."
3906 - name: subscription_id
3907 description: "The Azure subscription identifier."
3908 - name: resource_uid
3909 description: "The unique Azure resource identifier."
3910 metrics:
3911 - name: azure_monitor.service_bus.message_flow
3912 description: Azure Service Bus Message Flow
3913 unit: messages/s
3914 chart_type: line
3915 dimensions:
3916 - name: in
3917 - name: out
3918 - name: azure_monitor.service_bus.message_operations
3919 description: Azure Service Bus Message Operations
3920 unit: messages/s
3921 chart_type: line
3922 dimensions:
3923 - name: completed
3924 - name: abandoned
3925 - name: azure_monitor.service_bus.queue_depth
3926 description: Azure Service Bus Queue Depth
3927 unit: messages
3928 chart_type: line
3929 dimensions:
3930 - name: active
3931 - name: azure_monitor.service_bus.problem_messages
3932 description: Azure Service Bus Problem Messages
3933 unit: messages
3934 chart_type: line
3935 dimensions:
3936 - name: dead_lettered
3937 - name: scheduled
3938 - name: azure_monitor.service_bus.requests
3939 description: Azure Service Bus Requests
3940 unit: requests/s
3941 chart_type: line
3942 dimensions:
3943 - name: incoming
3944 - name: successful
3945 - name: azure_monitor.service_bus.errors
3946 description: Azure Service Bus Errors
3947 unit: errors/s
3948 chart_type: line
3949 dimensions:
3950 - name: server
3951 - name: user
3952 - name: throttled
3953 - name: azure_monitor.service_bus.connections
3954 description: Azure Service Bus Active Connections
3955 unit: connections
3956 chart_type: line
3957 dimensions:
3958 - name: active
3959 - name: azure_monitor.service_bus.connection_events
3960 description: Azure Service Bus Connection Events
3961 unit: connections
3962 chart_type: line
3963 dimensions:
3964 - name: opened
3965 - name: closed
3966 - name: azure_monitor.service_bus.namespace_size
3967 description: Azure Service Bus Namespace Size
3968 unit: bytes
3969 chart_type: line
3970 dimensions:
3971 - name: average
3972 - name: azure_monitor.service_bus.data_throughput
3973 description: Azure Service Bus Data Throughput
3974 unit: bytes/s
3975 chart_type: line
3976 dimensions:
3977 - name: in
3978 - name: out
3979 - name: azure_monitor.service_bus.total_messages
3980 description: Azure Service Bus Total Messages
3981 unit: messages
3982 chart_type: line
3983 dimensions:
3984 - name: total
3985 - name: azure_monitor.service_bus.namespace_resources
3986 description: Azure Service Bus Namespace Resources
3987 unit: percentage
3988 chart_type: line
3989 dimensions:
3990 - name: cpu
3991 - name: memory
3992 - name: azure_monitor.service_bus.send_latency
3993 description: Azure Service Bus Send Latency
3994 unit: milliseconds
3995 chart_type: line
3996 dimensions:
3997 - name: average
3998 - name: azure_monitor.service_bus.replication_lag
3999 description: Azure Service Bus Replication Lag
4000 unit: messages
4001 chart_type: line
4002 dimensions:
4003 - name: messages
4004 - name: azure_monitor.service_bus.replication_lag_duration
4005 description: Azure Service Bus Replication Lag Duration
4006 unit: seconds
4007 chart_type: line
4008 dimensions:
4009 - name: duration
4010 - name: azure_monitor.service_bus.checkpoint_operations
4011 description: Azure Service Bus Pending Checkpoint Operations
4012 unit: operations
4013 chart_type: line
4014 dimensions:
4015 - name: pending
4016 - <<: *module
4017 meta:
4018 <<: *meta
4019 id: collector-go.d.plugin-azure_monitor-application_gateway
4020 monitored_instance:
4021 name: Azure Application Gateway
4022 link: https://learn.microsoft.com/azure/application-gateway/
4023 icon_filename: azure.svg
4024 categories:
4025 - data-collection.cloud-and-devops
4026 keywords:
4027 - azure
4028 - application
4029 - gateway
4030 - load
4031 - balancer
4032 - waf
4033 overview:
4034 <<: *overview
4035 data_collection:
4036 metrics_description: |
4037 :::info
4038
4039 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
4040
4041 :::
4042
4043 Monitor Azure Application Gateway with metrics covering:
4044
4045 - **Traffic** -- throughput, traffic volume (received/sent), request rates (total/failed)
4046 - **Response** -- gateway and backend response status codes
4047 - **Backend** -- backend health (healthy/unhealthy hosts), backend latency (connect, first byte, last byte)
4048 - **Client** -- client latency (total time, client RTT)
4049 - **Connections** -- current and new connections, TLS connections, WebSocket connections
4050 - **Capacity** -- capacity units, compute units, billed/fixed billed, CPU utilization
4051 - **WAF** -- WAF requests (total/blocked/matched), rule matches (managed/custom/bot), challenges, penalty box
4052 method_description: *method_description
4053 alerts:
4054 - name: am_appgw_failed_requests
4055 metric: azure_monitor.application_gateway.requests
4056 info: "App Gateway failed requests on ${label:resource_name}"
4057 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf
4058 - name: am_appgw_unhealthy_hosts
4059 metric: azure_monitor.application_gateway.backend_health
4060 info: "App Gateway unhealthy backends on ${label:resource_name}"
4061 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf
4062 - name: am_appgw_backend_connect_time
4063 metric: azure_monitor.application_gateway.backend_latency
4064 info: "App Gateway backend connect time on ${label:resource_name}"
4065 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf
4066 - name: am_appgw_backend_first_byte
4067 metric: azure_monitor.application_gateway.backend_latency
4068 info: "App Gateway backend TTFB on ${label:resource_name}"
4069 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf
4070 - name: am_appgw_total_time
4071 metric: azure_monitor.application_gateway.client_latency
4072 info: "App Gateway total request time on ${label:resource_name}"
4073 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf
4074 - name: am_appgw_cpu_utilization
4075 metric: azure_monitor.application_gateway.cpu
4076 info: "App Gateway CPU utilization on ${label:resource_name}"
4077 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf
4078 - name: am_appgw_waf_blocked_ratio
4079 metric: azure_monitor.application_gateway.waf_requests
4080 info: "App Gateway WAF block ratio on ${label:resource_name}"
4081 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf
4082 metrics:
4083 folding:
4084 title: Metrics
4085 enabled: false
4086 description: ""
4087 availability: []
4088 scopes:
4089 - name: resource
4090 description: "These metrics refer to each monitored Azure resource."
4091 labels:
4092 - name: resource_name
4093 description: "The Azure resource name."
4094 - name: resource_group
4095 description: "The Azure resource group."
4096 - name: region
4097 description: "The Azure region where the resource is deployed."
4098 - name: resource_type
4099 description: "The Azure resource type identifier."
4100 - name: profile
4101 description: "The Azure Monitor profile basename."
4102 - name: subscription_id
4103 description: "The Azure subscription identifier."
4104 - name: resource_uid
4105 description: "The unique Azure resource identifier."
4106 metrics:
4107 - name: azure_monitor.application_gateway.throughput
4108 description: Azure Application Gateway Throughput
4109 unit: bytes/s
4110 chart_type: line
4111 dimensions:
4112 - name: average
4113 - name: azure_monitor.application_gateway.traffic_volume
4114 description: Azure Application Gateway Traffic Volume
4115 unit: bytes/s
4116 chart_type: line
4117 dimensions:
4118 - name: received
4119 - name: sent
4120 - name: azure_monitor.application_gateway.requests
4121 description: Azure Application Gateway Requests
4122 unit: requests/s
4123 chart_type: line
4124 dimensions:
4125 - name: total
4126 - name: failed
4127 - name: azure_monitor.application_gateway.response_status
4128 description: Azure Application Gateway Response Status
4129 unit: responses/s
4130 chart_type: line
4131 dimensions:
4132 - name: gateway
4133 - name: backend
4134 - name: azure_monitor.application_gateway.backend_health
4135 description: Azure Application Gateway Backend Health
4136 unit: hosts
4137 chart_type: line
4138 dimensions:
4139 - name: healthy
4140 - name: unhealthy
4141 - name: azure_monitor.application_gateway.backend_request_load
4142 description: Azure Application Gateway Backend Request Load
4143 unit: requests
4144 chart_type: line
4145 dimensions:
4146 - name: per_healthy_host
4147 - name: azure_monitor.application_gateway.backend_latency
4148 description: Azure Application Gateway Backend Latency
4149 unit: milliseconds
4150 chart_type: line
4151 dimensions:
4152 - name: connect
4153 - name: first_byte
4154 - name: last_byte
4155 - name: azure_monitor.application_gateway.client_latency
4156 description: Azure Application Gateway Client Latency
4157 unit: milliseconds
4158 chart_type: line
4159 dimensions:
4160 - name: total_time
4161 - name: client_rtt
4162 - name: azure_monitor.application_gateway.current_connections
4163 description: Azure Application Gateway Current Connections
4164 unit: connections
4165 chart_type: line
4166 dimensions:
4167 - name: current
4168 - name: azure_monitor.application_gateway.new_connections
4169 description: Azure Application Gateway New Connections
4170 unit: connections/s
4171 chart_type: line
4172 dimensions:
4173 - name: average
4174 - name: azure_monitor.application_gateway.websocket_connections
4175 description: Azure Application Gateway WebSocket Connections
4176 unit: connections
4177 chart_type: line
4178 dimensions:
4179 - name: active
4180 - name: azure_monitor.application_gateway.websocket_close_codes
4181 description: Azure Application Gateway WebSocket Close Codes
4182 unit: connections/s
4183 chart_type: line
4184 dimensions:
4185 - name: total
4186 - name: azure_monitor.application_gateway.capacity
4187 description: Azure Application Gateway Capacity
4188 unit: units
4189 chart_type: line
4190 dimensions:
4191 - name: capacity
4192 - name: compute
4193 - name: billed
4194 - name: fixed_billed
4195 - name: azure_monitor.application_gateway.cpu
4196 description: Azure Application Gateway CPU Utilization
4197 unit: percentage
4198 chart_type: line
4199 dimensions:
4200 - name: average
4201 - name: azure_monitor.application_gateway.tls_connections
4202 description: Azure Application Gateway TLS Connections
4203 unit: connections/s
4204 chart_type: line
4205 dimensions:
4206 - name: total
4207 - name: azure_monitor.application_gateway.waf_requests
4208 description: Azure Application Gateway WAF Requests
4209 unit: requests/s
4210 chart_type: line
4211 dimensions:
4212 - name: total
4213 - name: blocked
4214 - name: matched
4215 - name: azure_monitor.application_gateway.waf_rule_matches
4216 description: Azure Application Gateway WAF Rule Matches
4217 unit: matches/s
4218 chart_type: line
4219 dimensions:
4220 - name: managed
4221 - name: custom
4222 - name: bot
4223 - name: azure_monitor.application_gateway.waf_challenges
4224 description: Azure Application Gateway WAF Challenges
4225 unit: requests/s
4226 chart_type: line
4227 dimensions:
4228 - name: captcha
4229 - name: js_challenge
4230 - name: azure_monitor.application_gateway.waf_penalty_box
4231 description: Azure Application Gateway WAF Penalty Box
4232 unit: IPs
4233 chart_type: line
4234 dimensions:
4235 - name: size
4236 - name: azure_monitor.application_gateway.waf_penalty_box_hits
4237 description: Azure Application Gateway WAF Penalty Box Hits
4238 unit: hits/s
4239 chart_type: line
4240 dimensions:
4241 - name: total
4242 - <<: *module
4243 meta:
4244 <<: *meta
4245 id: collector-go.d.plugin-azure_monitor-key_vault
4246 monitored_instance:
4247 name: Azure Key Vault
4248 link: https://learn.microsoft.com/azure/key-vault/
4249 icon_filename: azure.svg
4250 categories:
4251 - data-collection.cloud-and-devops
4252 keywords:
4253 - azure
4254 - key
4255 - vault
4256 - secrets
4257 - certificates
4258 - security
4259 overview:
4260 <<: *overview
4261 data_collection:
4262 metrics_description: |
4263 :::info
4264
4265 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
4266
4267 :::
4268
4269 Monitor Azure Key Vault with metrics covering:
4270
4271 - **Availability** -- overall vault availability percentage
4272 - **API** -- API activity (hits/results), API latency
4273 - **Saturation** -- API saturation approaching service limits
4274 method_description: *method_description
4275 alerts:
4276 - name: am_key_vault_availability
4277 metric: azure_monitor.key_vault.availability
4278 info: "Key Vault availability on ${label:resource_name}"
4279 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_key_vault.conf
4280 - name: am_key_vault_api_latency
4281 metric: azure_monitor.key_vault.api_latency
4282 info: "Key Vault API latency on ${label:resource_name}"
4283 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_key_vault.conf
4284 - name: am_key_vault_saturation
4285 metric: azure_monitor.key_vault.saturation
4286 info: "Key Vault saturation on ${label:resource_name}"
4287 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_key_vault.conf
4288 metrics:
4289 folding:
4290 title: Metrics
4291 enabled: false
4292 description: ""
4293 availability: []
4294 scopes:
4295 - name: resource
4296 description: "These metrics refer to each monitored Azure resource."
4297 labels:
4298 - name: resource_name
4299 description: "The Azure resource name."
4300 - name: resource_group
4301 description: "The Azure resource group."
4302 - name: region
4303 description: "The Azure region where the resource is deployed."
4304 - name: resource_type
4305 description: "The Azure resource type identifier."
4306 - name: profile
4307 description: "The Azure Monitor profile basename."
4308 - name: subscription_id
4309 description: "The Azure subscription identifier."
4310 - name: resource_uid
4311 description: "The unique Azure resource identifier."
4312 metrics:
4313 - name: azure_monitor.key_vault.availability
4314 description: Azure Key Vault Availability
4315 unit: percentage
4316 chart_type: line
4317 dimensions:
4318 - name: average
4319 - name: azure_monitor.key_vault.api_latency
4320 description: Azure Key Vault API Latency
4321 unit: milliseconds
4322 chart_type: line
4323 dimensions:
4324 - name: average
4325 - name: azure_monitor.key_vault.saturation
4326 description: Azure Key Vault Saturation
4327 unit: percentage
4328 chart_type: line
4329 dimensions:
4330 - name: average
4331 - name: azure_monitor.key_vault.api_activity
4332 description: Azure Key Vault API Activity
4333 unit: operations/s
4334 chart_type: line
4335 dimensions:
4336 - name: hits
4337 - name: results
4338 - <<: *module
4339 meta:
4340 <<: *meta
4341 id: collector-go.d.plugin-azure_monitor-api_management
4342 monitored_instance:
4343 name: Azure API Management
4344 link: https://learn.microsoft.com/azure/api-management/
4345 icon_filename: azure.svg
4346 categories:
4347 - data-collection.cloud-and-devops
4348 keywords:
4349 - azure
4350 - api
4351 - management
4352 - gateway
4353 - apim
4354 overview:
4355 <<: *overview
4356 data_collection:
4357 metrics_description: |
4358 :::info
4359
4360 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
4361
4362 :::
4363
4364 Monitor Azure API Management with metrics covering:
4365
4366 - **Requests** -- gateway request rate
4367 - **Latency** -- request duration (overall and backend response time)
4368 - **Compute** -- gateway CPU and memory utilization
4369 - **Capacity** -- capacity utilization percentage
4370 - **Events** -- EventHub events (successful/failed/dropped/rejected/throttled/timed out), EventHub bytes sent
4371 - **WebSockets** -- WebSocket connection attempts, WebSocket messages
4372 - **Network** -- network connectivity status
4373 method_description: *method_description
4374 alerts:
4375 - name: am_api_management_capacity
4376 metric: azure_monitor.api_management.capacity
4377 info: "APIM capacity on ${label:resource_name}"
4378 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4379 - name: am_api_management_gateway_cpu
4380 metric: azure_monitor.api_management.gateway_cpu
4381 info: "APIM gateway CPU on ${label:resource_name}"
4382 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4383 - name: am_api_management_gateway_memory
4384 metric: azure_monitor.api_management.gateway_memory
4385 info: "APIM gateway memory on ${label:resource_name}"
4386 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4387 - name: am_api_management_request_duration
4388 metric: azure_monitor.api_management.request_duration
4389 info: "APIM request duration on ${label:resource_name}"
4390 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4391 - name: am_api_management_backend_duration
4392 metric: azure_monitor.api_management.request_duration
4393 info: "APIM backend duration on ${label:resource_name}"
4394 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4395 - name: am_api_management_network_connectivity
4396 metric: azure_monitor.api_management.network_connectivity
4397 info: "APIM network connectivity on ${label:resource_name}"
4398 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4399 - name: am_api_management_eventhub_failed_events
4400 metric: azure_monitor.api_management.eventhub_events
4401 info: "APIM EventHub failed events on ${label:resource_name}"
4402 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4403 - name: am_api_management_eventhub_dropped_events
4404 metric: azure_monitor.api_management.eventhub_events
4405 info: "APIM EventHub dropped events on ${label:resource_name}"
4406 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4407 - name: am_api_management_eventhub_rejected_events
4408 metric: azure_monitor.api_management.eventhub_events
4409 info: "APIM EventHub rejected events on ${label:resource_name}"
4410 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4411 - name: am_api_management_eventhub_throttled_events
4412 metric: azure_monitor.api_management.eventhub_events
4413 info: "APIM EventHub throttled events on ${label:resource_name}"
4414 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4415 - name: am_api_management_eventhub_timedout_events
4416 metric: azure_monitor.api_management.eventhub_events
4417 info: "APIM EventHub timed out events on ${label:resource_name}"
4418 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf
4419 metrics:
4420 folding:
4421 title: Metrics
4422 enabled: false
4423 description: ""
4424 availability: []
4425 scopes:
4426 - name: resource
4427 description: "These metrics refer to each monitored Azure resource."
4428 labels:
4429 - name: resource_name
4430 description: "The Azure resource name."
4431 - name: resource_group
4432 description: "The Azure resource group."
4433 - name: region
4434 description: "The Azure region where the resource is deployed."
4435 - name: resource_type
4436 description: "The Azure resource type identifier."
4437 - name: profile
4438 description: "The Azure Monitor profile basename."
4439 - name: subscription_id
4440 description: "The Azure subscription identifier."
4441 - name: resource_uid
4442 description: "The unique Azure resource identifier."
4443 metrics:
4444 - name: azure_monitor.api_management.capacity
4445 description: Azure API Management Capacity Utilization
4446 unit: percentage
4447 chart_type: line
4448 dimensions:
4449 - name: capacity
4450 - name: azure_monitor.api_management.gateway_cpu
4451 description: Azure API Management Gateway CPU
4452 unit: percentage
4453 chart_type: line
4454 dimensions:
4455 - name: cpu
4456 - name: azure_monitor.api_management.gateway_memory
4457 description: Azure API Management Gateway Memory
4458 unit: percentage
4459 chart_type: line
4460 dimensions:
4461 - name: memory
4462 - name: azure_monitor.api_management.requests
4463 description: Azure API Management Gateway Requests
4464 unit: requests/s
4465 chart_type: line
4466 dimensions:
4467 - name: requests
4468 - name: azure_monitor.api_management.request_duration
4469 description: Azure API Management Request Duration
4470 unit: milliseconds
4471 chart_type: line
4472 dimensions:
4473 - name: overall
4474 - name: backend
4475 - name: azure_monitor.api_management.eventhub_events
4476 description: Azure API Management EventHub Events
4477 unit: events/s
4478 chart_type: line
4479 dimensions:
4480 - name: total
4481 - name: successful
4482 - name: failed
4483 - name: dropped
4484 - name: rejected
4485 - name: throttled
4486 - name: timed_out
4487 - name: azure_monitor.api_management.eventhub_bytes
4488 description: Azure API Management EventHub Bytes Sent
4489 unit: bytes/s
4490 chart_type: line
4491 dimensions:
4492 - name: sent
4493 - name: azure_monitor.api_management.websocket_connections
4494 description: Azure API Management WebSocket Connection Attempts
4495 unit: attempts/s
4496 chart_type: line
4497 dimensions:
4498 - name: connection_attempts
4499 - name: azure_monitor.api_management.websocket_messages
4500 description: Azure API Management WebSocket Messages
4501 unit: messages/s
4502 chart_type: line
4503 dimensions:
4504 - name: messages
4505 - name: azure_monitor.api_management.network_connectivity
4506 description: Azure API Management Network Connectivity Status
4507 unit: status
4508 chart_type: line
4509 dimensions:
4510 - name: connectivity
4511 - <<: *module
4512 meta:
4513 <<: *meta
4514 id: collector-go.d.plugin-azure_monitor-front_door
4515 monitored_instance:
4516 name: Azure Front Door
4517 link: https://learn.microsoft.com/azure/frontdoor/
4518 icon_filename: azure.svg
4519 categories:
4520 - data-collection.cloud-and-devops
4521 keywords:
4522 - azure
4523 - front
4524 - door
4525 - cdn
4526 - waf
4527 - networking
4528 overview:
4529 <<: *overview
4530 data_collection:
4531 metrics_description: |
4532 :::info
4533
4534 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
4535
4536 :::
4537
4538 Monitor Azure Front Door with metrics covering:
4539
4540 - **Requests** -- client and origin request rates, origin shield requests (to shield/to origin/rate limited)
4541 - **Latency** -- total latency, origin latency
4542 - **Data transfer** -- request and response data transfer, origin shield data transfer, byte hit ratio
4543 - **Errors** -- 4xx and 5xx error rates
4544 - **Origin** -- origin health probe percentage
4545 - **WAF** -- WAF requests, challenges (CAPTCHA/JS challenge)
4546 - **WebSocket** -- WebSocket connections (requested/active), connection duration
4547 method_description: *method_description
4548 alerts:
4549 - name: am_front_door_origin_health
4550 metric: azure_monitor.front_door.origin_health
4551 info: "Front Door origin health on ${label:resource_name}"
4552 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf
4553 - name: am_front_door_total_latency
4554 metric: azure_monitor.front_door.latency
4555 info: "Front Door total latency on ${label:resource_name}"
4556 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf
4557 - name: am_front_door_origin_latency
4558 metric: azure_monitor.front_door.latency
4559 info: "Front Door origin latency on ${label:resource_name}"
4560 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf
4561 - name: am_front_door_5xx_error_rate
4562 metric: azure_monitor.front_door.error_rate
4563 info: "Front Door 5xx error rate on ${label:resource_name}"
4564 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf
4565 - name: am_front_door_4xx_error_rate
4566 metric: azure_monitor.front_door.error_rate
4567 info: "Front Door 4xx error rate on ${label:resource_name}"
4568 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf
4569 - name: am_front_door_byte_hit_ratio
4570 metric: azure_monitor.front_door.byte_hit_ratio
4571 info: "Front Door cache hit ratio on ${label:resource_name}"
4572 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf
4573 - name: am_front_door_waf_rate_limited
4574 metric: azure_monitor.front_door.origin_shield_requests
4575 info: "Front Door origin shield rate limiting on ${label:resource_name}"
4576 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf
4577 metrics:
4578 folding:
4579 title: Metrics
4580 enabled: false
4581 description: ""
4582 availability: []
4583 scopes:
4584 - name: resource
4585 description: "These metrics refer to each monitored Azure resource."
4586 labels:
4587 - name: resource_name
4588 description: "The Azure resource name."
4589 - name: resource_group
4590 description: "The Azure resource group."
4591 - name: region
4592 description: "The Azure region where the resource is deployed."
4593 - name: resource_type
4594 description: "The Azure resource type identifier."
4595 - name: profile
4596 description: "The Azure Monitor profile basename."
4597 - name: subscription_id
4598 description: "The Azure subscription identifier."
4599 - name: resource_uid
4600 description: "The unique Azure resource identifier."
4601 metrics:
4602 - name: azure_monitor.front_door.latency
4603 description: Azure Front Door Latency
4604 unit: milliseconds
4605 chart_type: line
4606 dimensions:
4607 - name: total
4608 - name: origin
4609 - name: azure_monitor.front_door.origin_health
4610 description: Azure Front Door Origin Health
4611 unit: percentage
4612 chart_type: line
4613 dimensions:
4614 - name: health
4615 - name: azure_monitor.front_door.byte_hit_ratio
4616 description: Azure Front Door Byte Hit Ratio
4617 unit: percentage
4618 chart_type: line
4619 dimensions:
4620 - name: hit_ratio
4621 - name: azure_monitor.front_door.error_rate
4622 description: Azure Front Door Error Rate
4623 unit: percentage
4624 chart_type: line
4625 dimensions:
4626 - name: 4xx
4627 - name: 5xx
4628 - name: azure_monitor.front_door.requests
4629 description: Azure Front Door Requests
4630 unit: requests/s
4631 chart_type: line
4632 dimensions:
4633 - name: client
4634 - name: origin
4635 - name: azure_monitor.front_door.data_transfer
4636 description: Azure Front Door Data Transfer
4637 unit: bytes/s
4638 chart_type: line
4639 dimensions:
4640 - name: request
4641 - name: response
4642 - name: azure_monitor.front_door.origin_shield_requests
4643 description: Azure Front Door Origin Shield Requests
4644 unit: requests/s
4645 chart_type: line
4646 dimensions:
4647 - name: to_shield
4648 - name: to_origin
4649 - name: rate_limited
4650 - name: azure_monitor.front_door.origin_shield_data_transfer
4651 description: Azure Front Door Origin Shield Data Transfer
4652 unit: bytes/s
4653 chart_type: line
4654 dimensions:
4655 - name: request
4656 - name: azure_monitor.front_door.waf_requests
4657 description: Azure Front Door WAF Requests
4658 unit: requests/s
4659 chart_type: line
4660 dimensions:
4661 - name: total
4662 - name: azure_monitor.front_door.waf_challenges
4663 description: Azure Front Door WAF Challenges
4664 unit: requests/s
4665 chart_type: line
4666 dimensions:
4667 - name: captcha
4668 - name: js_challenge
4669 - name: azure_monitor.front_door.websocket_connections
4670 description: Azure Front Door WebSocket Connections
4671 unit: connections/s
4672 chart_type: line
4673 dimensions:
4674 - name: requested
4675 - name: active
4676 - name: azure_monitor.front_door.websocket_duration
4677 description: Azure Front Door WebSocket Connection Duration
4678 unit: milliseconds
4679 chart_type: line
4680 dimensions:
4681 - name: average
4682 - <<: *module
4683 meta:
4684 <<: *meta
4685 id: collector-go.d.plugin-azure_monitor-vmss
4686 monitored_instance:
4687 name: Azure Virtual Machine Scale Set
4688 link: https://learn.microsoft.com/azure/virtual-machine-scale-sets/
4689 icon_filename: azure.svg
4690 categories:
4691 - data-collection.cloud-and-devops
4692 keywords:
4693 - azure
4694 - vmss
4695 - scale
4696 - set
4697 - virtual
4698 - machine
4699 - compute
4700 overview:
4701 <<: *overview
4702 data_collection:
4703 metrics_description: |
4704 :::info
4705
4706 This is part of the [Azure Monitor](/src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md) collector. No separate setup is needed -- a single Azure Monitor job discovers and monitors all supported resource types automatically.
4707
4708 :::
4709
4710 Monitor Azure Virtual Machine Scale Sets with metrics covering:
4711
4712 - **Compute** -- CPU utilization, CPU credits (consumed/remaining)
4713 - **Memory** -- available memory (bytes and percentage)
4714 - **Disk** -- IOPS, throughput, latency, and queue depth for OS, data, and temp disks
4715 - **Disk burst** -- burst credits and capacity for OS and data disks, VM-level cached/uncached burst credits
4716 - **Disk cache** -- premium OS and data disk cache hit/miss rates
4717 - **Network** -- traffic in/out, network flows, flow creation rate
4718 - **Availability** -- VMSS availability state
4719 - **Throttling** -- cached and uncached I/O bandwidth/IOPS throttling
4720
4721 Metrics are aggregated across all instances in the scale set.
4722 method_description: *method_description
4723 alerts:
4724 - name: am_vmss_cpu
4725 metric: azure_monitor.vmss.cpu
4726 info: "VMSS CPU utilization on ${label:resource_name}"
4727 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4728 - name: am_vmss_cpu_credits_remaining
4729 metric: azure_monitor.vmss.cpu_credits
4730 info: "VMSS CPU credits low on ${label:resource_name}"
4731 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4732 - name: am_vmss_memory_available
4733 metric: azure_monitor.vmss.memory_percentage
4734 info: "VMSS available memory low on ${label:resource_name}"
4735 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4736 - name: am_vmss_availability
4737 metric: azure_monitor.vmss.availability
4738 info: "VMSS availability degraded on ${label:resource_name}"
4739 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4740 - name: am_vmss_os_disk_latency
4741 metric: azure_monitor.vmss.os_disk_latency
4742 info: "VMSS OS disk latency on ${label:resource_name}"
4743 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4744 - name: am_vmss_os_disk_queue_depth
4745 metric: azure_monitor.vmss.os_disk_queue_depth
4746 info: "VMSS OS disk queue depth on ${label:resource_name}"
4747 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4748 - name: am_vmss_os_disk_bandwidth_throttling
4749 metric: azure_monitor.vmss.os_disk_throttling
4750 info: "VMSS OS disk bandwidth consumed on ${label:resource_name}"
4751 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4752 - name: am_vmss_os_disk_iops_throttling
4753 metric: azure_monitor.vmss.os_disk_throttling
4754 info: "VMSS OS disk IOPS consumed on ${label:resource_name}"
4755 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4756 - name: am_vmss_os_disk_burst_bps_credits
4757 metric: azure_monitor.vmss.os_disk_burst_credits
4758 info: "VMSS OS disk burst BPS credits depleting on ${label:resource_name}"
4759 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4760 - name: am_vmss_os_disk_burst_io_credits
4761 metric: azure_monitor.vmss.os_disk_burst_credits
4762 info: "VMSS OS disk burst IO credits depleting on ${label:resource_name}"
4763 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4764 - name: am_vmss_data_disk_latency
4765 metric: azure_monitor.vmss.data_disk_latency
4766 info: "VMSS data disk latency on ${label:resource_name}"
4767 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4768 - name: am_vmss_data_disk_queue_depth
4769 metric: azure_monitor.vmss.data_disk_queue_depth
4770 info: "VMSS data disk queue depth on ${label:resource_name}"
4771 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4772 - name: am_vmss_data_disk_bandwidth_throttling
4773 metric: azure_monitor.vmss.data_disk_throttling
4774 info: "VMSS data disk bandwidth consumed on ${label:resource_name}"
4775 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4776 - name: am_vmss_data_disk_iops_throttling
4777 metric: azure_monitor.vmss.data_disk_throttling
4778 info: "VMSS data disk IOPS consumed on ${label:resource_name}"
4779 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4780 - name: am_vmss_data_disk_burst_bps_credits
4781 metric: azure_monitor.vmss.data_disk_burst_credits
4782 info: "VMSS data disk burst BPS credits depleting on ${label:resource_name}"
4783 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4784 - name: am_vmss_data_disk_burst_io_credits
4785 metric: azure_monitor.vmss.data_disk_burst_credits
4786 info: "VMSS data disk burst IO credits depleting on ${label:resource_name}"
4787 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4788 - name: am_vmss_temp_disk_latency
4789 metric: azure_monitor.vmss.temp_disk_latency
4790 info: "VMSS temp disk latency on ${label:resource_name}"
4791 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4792 - name: am_vmss_temp_disk_queue_depth
4793 metric: azure_monitor.vmss.temp_disk_queue_depth
4794 info: "VMSS temp disk queue depth on ${label:resource_name}"
4795 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4796 - name: am_vmss_vm_cached_bandwidth_throttling
4797 metric: azure_monitor.vmss.vm_cached_throttling
4798 info: "VMSS cached bandwidth consumed on ${label:resource_name}"
4799 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4800 - name: am_vmss_vm_cached_iops_throttling
4801 metric: azure_monitor.vmss.vm_cached_throttling
4802 info: "VMSS cached IOPS consumed on ${label:resource_name}"
4803 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4804 - name: am_vmss_vm_uncached_bandwidth_throttling
4805 metric: azure_monitor.vmss.vm_uncached_throttling
4806 info: "VMSS uncached bandwidth consumed on ${label:resource_name}"
4807 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4808 - name: am_vmss_vm_uncached_iops_throttling
4809 metric: azure_monitor.vmss.vm_uncached_throttling
4810 info: "VMSS uncached IOPS consumed on ${label:resource_name}"
4811 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4812 - name: am_vmss_vm_cached_burst_bps_credits
4813 metric: azure_monitor.vmss.vm_cached_burst_credits
4814 info: "VMSS cached burst BPS credits depleting on ${label:resource_name}"
4815 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4816 - name: am_vmss_vm_cached_burst_io_credits
4817 metric: azure_monitor.vmss.vm_cached_burst_credits
4818 info: "VMSS cached burst IO credits depleting on ${label:resource_name}"
4819 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4820 - name: am_vmss_vm_uncached_burst_bps_credits
4821 metric: azure_monitor.vmss.vm_uncached_burst_credits
4822 info: "VMSS uncached burst BPS credits depleting on ${label:resource_name}"
4823 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4824 - name: am_vmss_vm_uncached_burst_io_credits
4825 metric: azure_monitor.vmss.vm_uncached_burst_credits
4826 info: "VMSS uncached burst IO credits depleting on ${label:resource_name}"
4827 link: https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf
4828 metrics:
4829 folding:
4830 title: Metrics
4831 enabled: false
4832 description: ""
4833 availability: []
4834 scopes:
4835 - name: resource
4836 description: "These metrics refer to each monitored Azure resource."
4837 labels:
4838 - name: resource_name
4839 description: "The Azure resource name."
4840 - name: resource_group
4841 description: "The Azure resource group."
4842 - name: region
4843 description: "The Azure region where the resource is deployed."
4844 - name: resource_type
4845 description: "The Azure resource type identifier."
4846 - name: profile
4847 description: "The Azure Monitor profile basename."
4848 - name: subscription_id
4849 description: "The Azure subscription identifier."
4850 - name: resource_uid
4851 description: "The unique Azure resource identifier."
4852 metrics:
4853 - name: azure_monitor.vmss.cpu
4854 description: Azure VMSS CPU Utilization
4855 unit: percentage
4856 chart_type: line
4857 dimensions:
4858 - name: average
4859 - name: azure_monitor.vmss.cpu_credits
4860 description: Azure VMSS CPU Credits
4861 unit: credits
4862 chart_type: line
4863 dimensions:
4864 - name: consumed
4865 - name: remaining
4866 - name: azure_monitor.vmss.memory
4867 description: Azure VMSS Available Memory
4868 unit: bytes
4869 chart_type: line
4870 dimensions:
4871 - name: available
4872 - name: azure_monitor.vmss.memory_percentage
4873 description: Azure VMSS Available Memory Percentage
4874 unit: percentage
4875 chart_type: line
4876 dimensions:
4877 - name: available
4878 - name: azure_monitor.vmss.availability
4879 description: Azure VMSS Availability
4880 unit: state
4881 chart_type: line
4882 dimensions:
4883 - name: average
4884 - name: azure_monitor.vmss.network_traffic
4885 description: Azure VMSS Network Traffic
4886 unit: bytes/s
4887 chart_type: line
4888 dimensions:
4889 - name: in
4890 - name: out
4891 - name: azure_monitor.vmss.network_flows
4892 description: Azure VMSS Network Flows
4893 unit: flows
4894 chart_type: line
4895 dimensions:
4896 - name: in
4897 - name: out
4898 - name: azure_monitor.vmss.network_flow_creation_rate
4899 description: Azure VMSS Network Flow Creation Rate
4900 unit: flows/s
4901 chart_type: line
4902 dimensions:
4903 - name: in
4904 - name: out
4905 - name: azure_monitor.vmss.disk_throughput
4906 description: Azure VMSS Disk Throughput
4907 unit: bytes/s
4908 chart_type: line
4909 dimensions:
4910 - name: read
4911 - name: write
4912 - name: azure_monitor.vmss.disk_iops
4913 description: Azure VMSS Disk IOPS
4914 unit: operations/s
4915 chart_type: line
4916 dimensions:
4917 - name: read
4918 - name: write
4919 - name: azure_monitor.vmss.os_disk_throughput
4920 description: Azure VMSS OS Disk Throughput
4921 unit: bytes/s
4922 chart_type: line
4923 dimensions:
4924 - name: read
4925 - name: write
4926 - name: azure_monitor.vmss.os_disk_iops
4927 description: Azure VMSS OS Disk IOPS
4928 unit: operations/s
4929 chart_type: line
4930 dimensions:
4931 - name: read
4932 - name: write
4933 - name: azure_monitor.vmss.os_disk_latency
4934 description: Azure VMSS OS Disk Latency
4935 unit: milliseconds
4936 chart_type: line
4937 dimensions:
4938 - name: average
4939 - name: azure_monitor.vmss.os_disk_queue_depth
4940 description: Azure VMSS OS Disk Queue Depth
4941 unit: operations
4942 chart_type: line
4943 dimensions:
4944 - name: average
4945 - name: azure_monitor.vmss.os_disk_throttling
4946 description: Azure VMSS OS Disk Throttling
4947 unit: percentage
4948 chart_type: line
4949 dimensions:
4950 - name: bandwidth
4951 - name: iops
4952 - name: azure_monitor.vmss.os_disk_burst_capacity
4953 description: Azure VMSS OS Disk Burst Capacity
4954 unit: bytes/s
4955 chart_type: line
4956 dimensions:
4957 - name: max_burst
4958 - name: target
4959 - name: azure_monitor.vmss.os_disk_burst_iops_capacity
4960 description: Azure VMSS OS Disk Burst IOPS Capacity
4961 unit: iops
4962 chart_type: line
4963 dimensions:
4964 - name: max_burst
4965 - name: target
4966 - name: azure_monitor.vmss.os_disk_burst_credits
4967 description: Azure VMSS OS Disk Burst Credits Used
4968 unit: percentage
4969 chart_type: line
4970 dimensions:
4971 - name: bandwidth
4972 - name: io
4973 - name: azure_monitor.vmss.data_disk_throughput
4974 description: Azure VMSS Data Disk Throughput
4975 unit: bytes/s
4976 chart_type: line
4977 dimensions:
4978 - name: read
4979 - name: write
4980 - name: azure_monitor.vmss.data_disk_iops
4981 description: Azure VMSS Data Disk IOPS
4982 unit: operations/s
4983 chart_type: line
4984 dimensions:
4985 - name: read
4986 - name: write
4987 - name: azure_monitor.vmss.data_disk_latency
4988 description: Azure VMSS Data Disk Latency
4989 unit: milliseconds
4990 chart_type: line
4991 dimensions:
4992 - name: average
4993 - name: azure_monitor.vmss.data_disk_queue_depth
4994 description: Azure VMSS Data Disk Queue Depth
4995 unit: operations
4996 chart_type: line
4997 dimensions:
4998 - name: average
4999 - name: azure_monitor.vmss.data_disk_throttling
5000 description: Azure VMSS Data Disk Throttling
Showing first 5,000 of 10,412 lines. View raw