This document summarizes a presentation on monitoring best practices. It recommends starting monitoring early in the development process during testing and staging rather than waiting until production. Monitoring should be integrated into continuous integration to gather metrics and detect issues early. The development team should be involved in setting up monitoring to ensure the right metrics are collected. The goal is to get a comprehensive view of system behavior and performance from an early stage using monitoring.

1. WWW.ICINGA.ORG
Icinga Open Source Monitoring
Icinga Camp
Amsterdam 2016
27 June - Team Icinga

2. Monitoring – The Open Source Way
MONITORING
When should you start?
Or
Metrics Led Development

3.  Working in IT since 1999.
 Icinga team member since 2011.
 Icinga Partner in Israel and UK.
 Nagios certified.
 Dog Lover.
 Whisky Connoisseur : www.maltgeeks.com
 Cyclist: https://www.strava.com/athletes/aflatto

`
`
Who Am I ?

4. Code
Servers
Code
CI
Test Led
Development

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

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

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

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

10. H
Things that Happen when we hit production.

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

12. Code
CI
Servers
Code
CI
Servers
Monitoring
Code
CI
Servers
Code
CI
Servers
Monitoring
Test Led
Development
Metrics Led
Development
!=

13. Code
CI
Servers
Monitoring
Code
CI
Servers
Monitoring
Metrics Led
Development

14. 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.
And more to the point – What NOT !!

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

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

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

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

21. 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

22. It is easy to start

23. Monitoring Hooks
Who knows what to look for ?
• Most often- the Person that wrote the code
How involved are they in the process ?
• Mostly,non at all
Paradigm Shift

24. Code
CI
Servers
Monitoring
Code
CI
Servers
Monitoring
Metrics Led
Development

25. 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.

26. m
Q/AContact Details:
WebSite: www.aikilinux.com
Email : assaf@aikilinux.com
Twitter: @aikilinux
Skype: aiki_linux
Linkedin:https://il.linkedin.com/in/assafflatto