The document discusses why monitoring systems currently have issues and how they could be improved. Some key problems identified are that monitoring tools are not consistent or adaptive to changing IT systems, they rely on outdated technologies, use simple mathematical models, lack timely and high-resolution data, have binary alerting, and provide limited opportunities for feedback. The document argues monitoring tools should be more intelligent, adaptive, and aim to reduce the need for expensive human experts.

1. why monitoring sucks
and how to improve it

3. monitoring sucks

4. actually…

5. monitoring sucks
%$§&ing big time!

6. why monitoring sucks
and how to improve it

7. zoo of incompletenesses

10. wow
very tools
much consistent
wow

11. monitoring is
too diverse
for one tool
to promise it all

12. to monitor means to
reason about
what you don’t
understand exactly

13. model written in stone

16. wow
very model
much adaptive
wow

17. IT systems
taxonomy and
geography
are continuously
moving parts

18. IT systems model
is a dynamic graph

19. outdated technology

22. wow
very technology
much modern
wow

23. technology is crucial
for (monitoring)
solutions

24. monitoring should fit
your technical future,
not your technical past

25. naïve math

28. wow
very math
much clever
wow

29. monitoring is a
mathematical domain

30. math is much more than
simple arithmetics

31. blind math

34. wow
very correlations
much semantic
wow

35. monitoring is
semantic knowledge

36. mathematical models
are crucial
(for monitoring)

37. eyeball intelligence

40. wow
very charts
much informative
wow

41. monitoring is a problem
that is very similar to
piloting aircrafts

42. let intelligent robots
support or partially
replace humans at
monitoring

43. weak resolution

46. wow
very pixels
much precise
wow

47. pixelation is
only good for
retro games and
for hiding

48. monitoring needs
default resolution <=1s,
higher resolution
on demand

49. not even
close to near time

52. wow
very realtime
much timely
wow

53. data that’s older than
previous second
is for forensics only

54. it needs to be
streaming
in order to be timely

55. forecasting
yesterday’s
weather

58. wow
very future
much forecast
wow

59. past events are good
for offline crunching
and post-mortems

60. today is only
yesterday’s tomorrow -
forecast based
prevention is more
effective than
hours long repair

61. ghost in the machine

64. wow
very cat
much Schrödinger
wow

65. let-it-crash and
bring-it-back

66. identification of
infrastructure elements
needs to be logic and
eventually probabilistic

67. binary alerting

70. wow
very cat
much Schrödinger
wow

71. false-positives and
false-negatives
are there to learn

72. user needs to help
turn false into true

73. feedback monologue

76. wow
very feedback
much easy
wow

77. feedback is not
configuration or code,
it’s a click

78. feedback is there
to learn

79. misplaced intelligence

82. wow
very business
much intelligent
wow

83. stable operations is a
business requirement,
but not a business focus

84. trying to reason about
business by looking at
systems is wrong

85. need for
.1%

88. wow
very expertise
much dollar
wow

89. performance and
monitoring experts are
rare and expensive

90. it should be tools that
replace them, not tools
that legitimate their
daily rates

91. monitoring sucks
but it can be improved

92. thank you
@pavlobaron
@instanahq