I'm working as a contractor for an organization where the technical team is of the opinion that easy is not better. I'm showing then the value of using a SEIM that allows drilling down and their response was that they prefer one that uses CLI so that the team keeps up their skills. So for them I fear that automation will need to be pursued as a challange rather than as the benefits that it brings.
It would be handy if I could schedule a recurring maintenance period for a node without having to delve into setting up a Windows Scheduled Task or a cron job with API call.
Wow, you may have described an attitude that I have run into perfectly. I have had luck persuading some to change - a well designed GUI that was quicker to use than a script. But overall, I feel your pain.
Limited and mindful automation is the way to go, in my experience. If you try to automate everything, invariably you either miss something, or you end up being in a situation where something fundamental changes within the automation stack, and it breaks a lot of your work.Like everything else, use automation as a tool, but be careful where you apply it!
\m/