OSMC 2014: Why we do monitoring wrong | Michael Medin
In many IT fields we have in the past decade seen a truly revolution in terms of changes whereas others have been slow (I am looking at you leading open source monitoring tool). I think it is high time for a revolutionary change and more importantly I think it is time for monitoring to become not only a tool for the IT support team but for the entire enterprise. This will NOT be about some fancy new monitoring tool or even about NSClient++. Instead I will show how we can change the tools we use today to make monitoring a bit more modern and take it into the new millennia (yes, the one we are already in). ...But since I have added which I think is the coolest feature ever to NSClient++ I might (if I have time) spend 5 minutes (at the end) showing the new WEB UI for NSClient++ :)
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Recently uploaded
Recently uploaded (20)
OSMC 2014: Why we do monitoring wrong | Michael Medin
- 1. Wrong Why we do
- 2. …frustration… dev not ops
- 11. Please don’t be angry! Some times I am busy
- 15. TAKE:1
- 16. check_disk -w 80 –c 90
- 17. Slack -w 80 –c 90 1gb 1tb 1pb 0.2g 219g 225 179g
- 18. Better? -w $ARG1$ 1gb 1tb 1pb 0.2g 22g 2 251g 80% 98% 99,8% Magic?
- 19. 0 500 1000 1500 2000 2500 3000 Value Warning Critical The problem The first alert On call staff alerted Lost time Things went bad!
- 20. 0 500 1000 1500 2000 2500 3000 Value Warning Critical The problem The first alert On call staff alerted Lost time
- 21. No Slack -w trend-line 1gb 1tb 1pb 0g 0g 0g
- 22. Works With Everything! Magic?
- 23. TAKE:2
- 24. planning What about Capacity Bounds?
- 25. Alarm clock
- 26. 0 500 1000 1500 2000 2500 Warning Critical HDD 1 HDD 2 Full How long? > 80% > 90%
- 27. 0 500 1000 1500 2000 2500 Warning Critical HDD 1 HDD 2 Full warn=full in less than x weeks
- 28. Photo Credit Howard Dickins Alarm clock 2 hours before work
- 29. 0 500 1000 1500 2000 2500 3000 Value Warning Critical The first alert On call staff alerted
- 30. No basic math! Magic?
- 32. check_disk -w 80 –c 90
- 33. 0 500 1000 1500 2000 2500 Value Warning Critical Backup check_disk check_disk_backup
- 34. 0 500 1000 1500 2000 2500 Value Warning Critical check_disk warn=usage>80% and not_backup Backup
- 35. No it is tags Magic?
- 36. Other TAKE:1
- 37. check_load -w 1 –c 2
- 38. Bad CPU load? 80% 90% 100% 0%
- 39. 0 10 20 30 40 50 60 70 80 90 100 Value Yesterday Last Week
- 40. No, still math Magic?
- 42. check_load -w 1 –c 2
- 43. High Load ??? GOOD BAD DO WE CARE?
- 45. No, still math Magic?
- 46. TAKE:2
- 47. check_mem -w 80 –c 90
- 48. Bad Memory? 80% 90% 100% 0%
- 49. Managed… Java JVM .net CLR
- 50. check_mem check_jmx check_counter check_wmi
- 51. check_disk -w 80 –c 90
- 52. FULL DISK ??? GOOD BAD DO WE CARE?
- 53. Because we can? Why do we monitor? Because we do? Because…
- 55. IT BUSINESS
- 56. No, common sense Magic?
- 57. TAKE:1
- 58. Nagios™ is Old Easy Simple What we always do
- 59. bischeck Addons Other solutions “the new stuff” forks
- 60. Why a tool? fast forward 15 years Nagios™ Naemoncould do this! Why an addon?
- 61. cron */5 * * * * wrap.sh mycheck #!/bin/bash $* if [ $? == 1 ];then send-email.sh fi;
- 64. TAKE:2
- 67.
- 69. TAKE:1
- 72. TAKE:2
- 73. Photo by Olga Berrios
- 74. Information about NSClient++ http://nsclient.org facebook.com/nsclient Slides, and examples http://nsclient.org/nscp/conferances My Blog http://blog.medin.name