Metrics led development is a method of developing your monitoring along side your code the same way you develop your CI.

1. Monitoring – The Open Source Way
MONITORING
when should you start?

2. 
Working in IT since 1999

Icinga team member since 2011

Nagios certified

Dog Lover, Crazy cyclist

Whisky Connoisseur – www.maltgeeks.com

My Site: www.aikilinux.com
Who Am I ?

3. Why do you want monitoring?
Know the state of the server.
Know the state of the service/product you provide.
Be able to anticipate issues before clients are
aware of them (proactive).

4. When Do Most Companies Start Monitoring?
• When a Client calls about a problem.
• Staging / Pre-Production
• Production.
• When the management is
asking for reports about SLA.

5. When should you start monitoring?
QA
Load Testing
E2E Testing
Staging

6. Monitoring = Day 2
Monitoring starts when your code is first
tested!!

7. Why Do You NEED Monitoring?
Know the state of the server.
Know the state of the service/product you provide.
Be able to anticipate issues before clients are aware of them (proactive).
Gather behavioural data about the system.
Learn about bottlenecks in the system and plan to avoid them.
Tracking the changes that happen on the system.

8. Know your code/system

11. H
Things that Happen when we hit production.

12. How do you go about setting up monitoring ?
Market research to select which tool to use.
And many more Tools...

13. What do we want to monitor ?
Laptops ? Servers? VoIP Phones?
Printers? Switches? PBX ?
Storage? FireWalls?
Routers? AP's ?
Before we select the tool, we need to define the
scope of what to include.

15. Capabilities
What capabilities does the tool support ?
SNMP Added custom checks
Active/passive results Database integration
H/A Scaling
Distributed monitoring

16. Support ?
Community
Professional
Dedicated support personnel.
Provides SLA.
Known entity to communicate with.
Not depended on the “kindness of others”

17. • Use an external service.
• Hire external consultants.
• Build a full NOC.
How do you go about setting up
monitoring? – cont.

18. Use the tool you know
For Against
 Fast implementation “waste time for DEV system”
 Easy to set up “will not be the real product”
 Easy to hand over
 You don't care – it is for data
gathering

19. It is easy to start

20. Monitoring Hooks
Who knows what to look for ?
• The Person that wrote the code (most often)
How involved are they in the process ?
• Mostly – non at all – must change!!

21. Conclusion
* Start monitoring early.
* Involve Dev in the monitoring process.
* Make it part of CI (same as Unit testing).
* Gather as much data as possible, as early as
possible.
* Expose the data to the management and
architects.
* Always highlight any abnormal occurrence.

22. m
Q/A
Email :assaf@aikilinux.com
Twitter: @aikilinux