error when creating "windows-exporter-daemonset.yaml": namespaces "monitoring" not found

[mloskot]

The instruction to kubectl apply -f windows-exporter-daemonset.yaml does not mention any requirements to create a new namespace, but it looks like it expects monitoring namespace. From https://github.com/prometheus-community/windows_exporter/blob/10e42d3583523912bdb1f1af8bb28d6de174a4d3/kubernetes/windows-exporter-daemonset.yaml#L3-L7

apiVersion: apps/v1
kind: DaemonSet
metadata:
  labels:
    app: windows-exporter
  name: windows-exporter
  namespace: monitoring
...

while https://github.com/Azure/prometheus-collector/blob/05bec023933ade8b3d5f6032031f9411da906f20/otelcollector/configmaps/ama-metrics-settings-configmap.yaml#L56-L58

metadata:
  name: ama-metrics-settings-configmap
  namespace: kube-system

Is this namespaces mismatch?

The Verify deploymnet commands refer to kube-system namespace.

Please, update the documentation with complete steps required to enable Windows metrics collection.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 58a1690b-c20f-b07e-29b9-1a8f98528114
• Version Independent ID: c58b4d70-1b2f-166f-8a23-935410e23ca9
• Content: Enable Azure Monitor managed service for Prometheus - Azure Monitor
• Content Source: articles/azure-monitor/essentials/prometheus-metrics-enable.md
• Service: azure-monitor
• Sub-service: essentials
• GitHub Login: @EdB-MSFT
• Microsoft Alias: edbaynash

[SaibabaBalapur-MSFT]

@mloskot Thanks for your feedback! We will investigate and update as appropriate.

[AnuragSingh-MSFT]

@mloskot, thank you for the feedback. I am assigning it to our content team for further review/update, as required.

@EdB-MSFT, could you please review this issue and share your feedback.

[jsturtevant]

@bragi92 do you know the correct namespace for this to work with Azure monitor scraper?

[mloskot]

Hmm, @jsturtevant, do you mean name used in the manifest for namespace: monitor is in any way relevant for the Azure Monitor to work properly?

[EdB-MSFT]

@bragi92 ?

[EdB-MSFT]

reassign:bragi92

[jsturtevant]

Hmm, @jsturtevant, do you mean name used in the manifest for namespace: monitor is in any way relevant for the Azure Monitor to work properly?

Yes, it looks like azure monitor scraper is in a different namespace than the exporter with would mean it might not have RBAC Permissions to scrape it. I would guess that if you deploy the exporter into kube-system (based on the configmap you shared) that you might begin to get data. This is a guess on my part.

[EdB-MSFT]

please-close