tools: Machine audit - backend scripts to run on Nagios server#4357
tools: Machine audit - backend scripts to run on Nagios server#4357Haroon-Khel wants to merge 19 commits into
Conversation
| scp_command = [ | ||
| "scp", | ||
| "-P", port, | ||
| "-o", "StrictHostKeyChecking=no", |
There was a problem hiding this comment.
Semgrep will likely flag this as an issue, might be worth trying it without this flag.
|
The nagios server was able to collect the machine_info.json file from 46 of our machines (static nodes included, windows machine excluded for now). Some connection issues, on other failing machines the machine_info.json file wasnt present. Still good progress. All thats left with this pr is the windows machines |
|
For windows, copying the machine_info.json file from the remote windows nodes onto the nagios server will be tricky since it wont respond to scp. Can be solved with a playbook which first runs the platform/windows.ps1 script on the windows nodes, and then at the end of the playbook copies the output machine_info.json file to the local host to forward it onto the nagios server's backend/collectedInfo directory |
|
The windows playbook needs these connection variables to run (found in the adoptium windows playbook vars file) |
Re #4334
Backend scripts to run on the Nagios server.
collecedInfo/{node_name}_machine_info.jsonprovided as command line arguments for now.pass in via .env filelinux_aix_audit.ymlexecutes platforms/linux.py and aix.py on linux and aix nodesstatic_docker_audit.ymlexecutes platforms/linux.py on static containers running on dockerhost nodes.Both playbooks will run in scheduled jobs in AWX
Things i need to do to test this pr:
machine_info.jsonon each machine