Summary

• Corrects the Windows Event Logs prerequisites in integrations/logs/metadata.yaml
• Changes "Netdata Cloud paid subscription" to "A Netdata Cloud account"
• Ensures consistency with other log integrations (systemd journal, OpenTelemetry)
• Reflects that Windows Events is available on the free Community tier

Changes

Updated the prerequisites section for the Windows Event Logs integration to accurately state that only a Netdata Cloud account is required, not a paid subscription. This aligns with:

• The Access Control documentation confirming Windows Events is available on the Community tier
• The Plugin Reference documentation stating "a free Netdata Cloud user account is required"
• The prerequisite wording used by other log integrations

Audit Context

Session Query: capture logs from windows events into netdata

Decision Verdict: surgical_edit - The answer is factually correct - Windows Events plugin requires only a FREE Netdata Cloud account, not a paid subscription. However, there is a documentation contradiction: the generated Windows Event Logs overview page (sourced from metadata.yaml) incorrectly states 'Netdata Cloud paid subscription' as a prerequisite, while the Plugin Reference README and the authoritative Access Control documentation both confirm that Windows Events is available on the free Community tier.

Test Plan

• Verify line 74 in metadata.yaml reads "- A Netdata Cloud account"
• Confirm wording matches other log integrations
• Verify generated documentation shows correct prerequisite after regeneration

Summary by cubic

Fixes the Windows Event Logs prerequisite in integrations/logs/metadata.yaml to say “A Netdata Cloud account” instead of “paid subscription.” This aligns the generated docs with Access Control and other log integrations, reflecting availability on the free Community tier.

^{Written for commit d9870aa. Summary will update on new commits.}