New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Azure][compute_vm][compute_vm_scaleset] metrics Azure.VM.Windows.GuestMetrics
and Azure.VM.Linux.GuestMetrics
seems to be not available
#7167
Comments
Azure.VM.Windows.GuestMetrics
and Azure.VM.Linux.GuestMetrics
seems to be not not availableAzure.VM.Windows.GuestMetrics
and Azure.VM.Linux.GuestMetrics
seems to be not available
@zmoog @tommyers-elastic could you help me with this? |
I was missing some extra configuration: |
thanks tania! do you think the docs need improving here? |
@tommyers-elastic yes, the only documentation I found is this - https://docs.elastic.co/integrations/azure_metrics/compute_vm#guest-metrics |
later I also found this https://github.com/elastic/beats/pull/20631/files with link to https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/collect-custom-metrics-guestos-resource-manager-vm, here is at least mentioned data sink |
@tetianakravchenko so the issue is resolved with these extra settings? The docs are there, but it would be great if they were more precise and actionable. |
yes, actually to be more precise required steps are:
|
compute_vm
- current configuration - https://github.com/elastic/integrations/blob/main/packages/azure_metrics/data_stream/compute_vm/agent/stream/stream.yml.hbs#L100-L150 that includesnamespace: "Azure.VM.Linux.GuestMetrics"
andnamespace: "Azure.VM.Windows.GuestMetrics"
Note: I've configured diagnostic settings on all monitored nodes as described in https://docs.elastic.co/integrations/azure_metrics/compute_vm#guest-metrics:
But I am not getting any metrics and also I see those elastic-agent errors:
the same for linux:
For the
compute_vm_scaleset
I see the same behavior - error:I am missing a guidance how to get those metrics
The text was updated successfully, but these errors were encountered: