I have a bunch of windows and linux instances which are running various checks across namespaces but i see the following error on windows instances when the checks are tried to run.
This happens particularly with Windows instances when the checks are not present at the target instance location and therefore the agent is not able to run the check. My understanding of the working of the sensu go architecture is that checks are passed from the backend to the agent for it to execute on the agent instance and therefore should not need the checks present locally. This error generally means the command was run on windows command line (not powershell) and the command file does exist.
The check in the image uses the asset check-memory-usage versions (renamed to window-mem-plugin for the following example) which is meant to work across OS. Check definition is as follows.
command: check-memory-usage -w 80 -c 95 runtime_assets: - windows-mem-plugin subscriptions: - windows
This thread is similar to Newbie question...How to add Sensu Checks on Windows but the previous thread was for Sensu EOL where the architecture required the destination instance to have the checks on the instance.
Sensu backend is 6.1.0 (on a Centos 7 instance) and Sensu agent is 6.2.3 on Windows 2016 instance. Both backend and agent are hosted on different AWS machines
No github issue was created on the plugin github repo since this is possibly a Sensu execution issue and not the plugin itself