Skip to content
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

Closed
tetianakravchenko opened this issue Jul 27, 2023 · 7 comments

Comments

@tetianakravchenko
Copy link
Contributor

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 includes namespace: "Azure.VM.Linux.GuestMetrics" and namespace: "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:
Screenshot 2023-07-27 at 17 10 49

But I am not getting any metrics and also I see those elastic-agent errors:

no metric definitions were found for resource /subscriptions/XXXX/resourceGroups/XXXX/providers/Microsoft.Compute/virtualMachines/XXX and namespace Azure.VM.Windows.GuestMetrics. Verify if the namespace is spelled correctly or if it is supported by the resource in case.

the same for linux:

no metric definitions were found for resource /subscriptions/XXXX/resourceGroups/XXXX/providers/Microsoft.Compute/virtualMachines/XXXX and namespace Azure.VM.Linux.GuestMetrics. Verify if the namespace is spelled correctly or if it is supported by the resource in case.

For the compute_vm_scaleset I see the same behavior - error:

no metric definitions were found for resource /subscriptions/XXXX/resourceGroups/XXXX/providers/Microsoft.Compute/virtualMachineScaleSets/XXX and namespace Azure.VM.Windows.GuestMetrics. Verify if the namespace is spelled correctly or if it is supported by the resource in case.

I am missing a guidance how to get those metrics

@tetianakravchenko tetianakravchenko changed the title [Azure][compute_vm][compute_vm_scaleset] metrics Azure.VM.Windows.GuestMetrics and Azure.VM.Linux.GuestMetricsseems to be not not available [Azure][compute_vm][compute_vm_scaleset] metrics Azure.VM.Windows.GuestMetrics and Azure.VM.Linux.GuestMetrics seems to be not available Jul 27, 2023
@tetianakravchenko
Copy link
Contributor Author

tetianakravchenko commented Jul 27, 2023

@zmoog @tommyers-elastic could you help me with this?

@tetianakravchenko
Copy link
Contributor Author

tetianakravchenko commented Jul 28, 2023

I was missing some extra configuration:
was fixed for the compute_vm_scaleset by: Diagnostic settings > under Sinks > Enable Azure Monitor

@tommyers-elastic
Copy link
Contributor

thanks tania! do you think the docs need improving here?

@tetianakravchenko
Copy link
Contributor Author

@tommyers-elastic yes, the only documentation I found is this - https://docs.elastic.co/integrations/azure_metrics/compute_vm#guest-metrics

@tetianakravchenko
Copy link
Contributor Author

@zmoog
Copy link
Contributor

zmoog commented Jul 28, 2023

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

@tetianakravchenko
Copy link
Contributor Author

@zmoog

@tetianakravchenko so the issue is resolved with these extra settings?

yes, actually to be more precise required steps are:

  • on vm resource under Monitoring > Install Diagnostics Extension
    • select storage account - you might need to create a Diagnostics storage account if does not exist already
    • enable guest-level monitoring
  • Diagnostic settings > Sinks > Enable Azure Monitor
    note: to do so should be configured managed identity:
Screenshot 2023-07-28 at 17 26 01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants