The case for Monitoring

(Food for thought)


Nir Cohen @ Gigaspaces

nir0s @ GitHub



  • Cultural Aspects
  • The case for Open-Source
  • Enabling Automation

Cultural Aspects in Monitoring

Everyone owns monitoring

(not just Ops)

Discuss system state periodically and adjust

(not just once)

Monitoring should be part of the application

(not an after-thought)

Work towards prevention

(not fire-hosing)

Be open to change

(otherwise you can't progress)

Be open to open-source

(free isn't necessarily bad)

The case for open-source

Huge ecosystem, loads of tools

On-going support by the community

More transparent future

Contributing back

Monitoring Enables Automation

Continuous Deployment




Monitoring Continuously Evolves


Monitoring systems must be more available and scalable than the systems being monitored


​Monitoring is hard. You can simplify it only so much before its value decreases.


  • Continuous Delusions (Avishai Ish-Shalom@Velocity) -
  • Why Percentiles don't work the way you think -
  • InfluxData -
  • The Math Behind Bad Behavior -
  • Stream Processing... -
  • Incuriousity will kill your infrastructure -
  • Practical Guide to StatsD/Graphite Monitoring -
  • How we scaled our monitoring platform -
  • 5 years of metrics and monitoring -
  • Please, no more minutes, milliseconds, monoliths or monitoring tools -
  • StatsCraft 2015 Sessions -
  • Monitorama Sessions -

The case for Monitoring

By Nir Cohen

The case for Monitoring

  • 1,016