Ignite SessionDevOpsDays TLV 2015

Monitoring that will make your engineers give up

Gil Zellner (CloudifyDev at Gigaspaces)

tl;dr

Why is monitoring so important ?

solution: alert only things that meet the following criteria:

1) actionable - can I do something about this?2) does this currently or immediately break the business?3) this cannot wait till morning

Next day

2nd Deadly sin of monitoringSingle team does monitoring, everyone else is second tier

Solution: direct alerts to relevant parties1) only person who can fix the problem gets alerted, others get emails2) system needs to be smart enough to make the choice, and fixed when it

makes a mistake in waking up the wrong person

Alerte générale!

Solution: Monitoring needs to be a part of the designthe empty error - classic example - null pointer exceptions in java

make your developers accountable for empty errors

solutions:self correcting metrics. if an alert goes off for a metric, and we decide it wasn’t a real error - a dialog for changing the threshold should pop up.

solution example: netflixstarts per minute

Bad artists copy, great artists steal

We’re hiring:

http://jobs.gigaspaces.com/ email:Gil.Zellner@gmail.com

Twitter: @Heathenaspargus