saltstack / saltstack/salt

Request for Windows Beacons

Open
#52,270 4 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Confirmed Epic Feature Windows
Dominant language
Python
Stars
15.7k
Forks
5.6k
Avg merge
2d 44m
Merged PRs (30d)
80

Description

Description of Issue/Question

Scoping/Effort estimation for Windows Beacons

On Linux machines we have an iNotify beacon that makes it easy to watch for an identify when a change happens on a machine and kick off the a config drift remediation process.

But there is no iNotify functionality on Windows & Unix systems that can be used to create a similar event generation to kick off the event orchestration.

This beacon would be a great starting point for many PoCs or initial projects it is also a perfect beacon for demonstrations on these operating systems.

  1. Establish a list of beacons already supported on Windows
    Is Memusage supported ? - https://github.com/saltstack/salt/pull/38584
  2. Based on Windows customer use-cases, below is the prioritized list of some Linux beacons that would be useful for Windows users as well. Lets scope/estimate for each of below items individually:
    File - iNotify
    Service
    disk usage/log
    Load
    Network_settings
    Network_info
    Memusage

After talking to dev team, it was confirmed that Service, disk usage/log, memusage and Network_info are already supported.

Related links

http://ibmsystemsmag.com/blogs/aixchange/august-2015/helpful-links-about-event-monitoring/
https://blogs.msdn.microsoft.com/commandline/2016/10/07/wsl-adds-inotify-filesystem-change-notification-support/
https://github.com/emcrisostomo/fswatch

Other relevant Issues that requests Windows Beacon support
Load: https://github.com/saltstack/salt/issues/38463
https://github.com/saltstack/salt/issues/31916

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.