Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Are you still alive? Bringing monitoring to te ...

Are you still alive? Bringing monitoring to te devs

Monitoring is not a ops native topic anymore. For scaling purposes monitoring your infrastructure and application behaviour needs to be a dev native task.

Avatar for Alex Gläser

Alex Gläser

November 18, 2018

Other Decks in Technology

Transcript

  1. The Journey 2014 – The year of basic monitoring 2016

    – The year of advanced (application) monitoring 2017 – Massive scale out (100+ Mio events a day) 2018+ – Adpot for devs and stages
  2. Ok, but now? Adopt to and for your devs •

    „There‘re entries getting lost – could we monitor?“ - Last weeks story of a devs request Get the most early feedback of your products Performance issue analysis + detection
  3. DEV Enablement Monitoring and its management is not an ops

    native topic anymore For scaling: Enable devs for self managed monitoring • Pilot kickoff last week to enable specific dev (and QA) teams @CGM for self managed monitoring For standardization • Implement USE and RED methods
  4. Monitoring For Free? <sarkasm> Yes, for sure: - All tools

    are free of charge - Don‘t plan time for devs to manage monitoring - Don‘t extend next years budget for monitoring </sarkasm>
  5. Management Is Around The Corner Monitoring vs. Reporting • Be

    careful – draw a line between both • Monitoring != Reporting • Monitoring for the management – Why not?!
  6. Monitoring – Alerting - OCS Implementing OCS • On call

    service is not an ops topic anymore • Are your devs 24/7 OCS ready? • OCS is the best way to get your alerting bullet proof