DevOps
We Gave Our Release Pipeline a Train Conductor (and Built It in Days)
Improving the On-Call Experience with Alert Management thenewstack.io
I'm very pro monitoring and pre-emptive alerting, but these alerts have to be relevant and the monitoring has to be of the correct thicorrectngs.
The expectation with monitoring is that when you’re paged, the issue is urgent, real and requires your direct investigation and intervention. But the gap between that expectation and reality is bigger than the Grand Canyon: 59% of surveyed cloud native developers reported that only half of the alerts they receive are helpful or usable.
DevOps: Where it's going and how to make the most of it zdnet.com
Just a great quote form a good article. I see a lot of teams getting bogged down in trying to boil the ocean to solve problems, when a few smart moves can make a big difference.
There's a difference between being on the bleeding edge and being a successful follower. You don't have to keep inventing new things, but you do have to react quickly.
Using Slack To Monitor Your App smashingmagazine.com
We've been using slack integrations with our git repos, Jenkins, Jira and are looking at integrations with AppDynamics and some extreme feedback items. We found it incredibly helpful for our team members on support to create some custom Hubot scripts. These tell support things like what time it is on the ship, what version of the application is deployed, how much memory and how many processes things like Apache, MySQL, and Node.js have.
As my curiosity grew with each ding, I began to wonder things like, What if there was a failure to create a new user? What if a user registered, logged in but didn’t complete the onboarding process? What is the result of our scheduled tasks? Now that the groundwork was in place, answering these questions was a piece of cake.