Hi there
There' obviously the CI tool (CircleCI in our case, but there are so many out there).
(Most of our code is NodeJS, and we use the usuall tools there with mocha, chai, ...)
As we're in the process of preparing moving a lot to Kubernetes, we're investing in Helm right now to manage releases
All our logs are sent to Loggly, on which we do have (too?) many alerts
Our metrics (from web servers, workers, but also db servers, nginx, rabbitmq...) are also sent to Datadog, on which we have some other alerts
All alerts are sent to a dedicated Slack channel.
Critical alerts also triggered Pagerduty tickets for the on-call team. (We're a small team, so there's only a single on-call group)
Then I'd like to mention some other tools we built/leverage to help us doing
AWS Lambda can be triggered by CLoudwatch Cron events, which makes a super cheap (as in almost free), secure and resilient way to run administrative cron task. In this case, this Cloudwtach cron event trigger a lambda which start a on-off task in ECS (which we'll probably later move to a Kubernetes Job). This weekly job is built in-house (Python and Docker there) to shallow-clone all the repositories from our org, and run vulnerability scans against them (with Snyk and NSP), format the reports and post them to Slack. We used this approach to get a cheap and 0-maintenance way to scan any repos, public or private, and make sure even the new repo created will be scanned, without the need to do any setup.
Bottom line for your automation needs: Cloudwatch scheduled events are usually overlooked, but imho Cloudwtach scheduled events+lambda should replace traditional cron jobs most of the time!
There's probably many other things I take for granted and I forget to mention there,
Sébastien Portebois
Software architect at Ubisoft