New chapter: monitoring

content/books/things-i-learnt/_index.md

@@ -51,6 +51,7 @@ template = "section-contentless.html"
 		* [Always Use Timezones With Your Dates](use-timezones)
 		* [Always Use UTF-8 For Your Strings](use-utf8)
 		* [Logs Are For Events, Not User Interface](log-events)
+		* [Learn To Monitor](monitoring)
 * Community/Teams
 	* [A Language Is Much More Than A Language](languages-are-more)
 	* [Understand And Stay Away From Cargo Cult](cargo-cult)

content/books/things-i-learnt/languages-are-more/index.md

@@ -54,4 +54,4 @@ And picking a language for something _above_ the syntax is even worse.
   tool." So, basically, the community ignored whatever the community was
   using.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/log-events", prev_chapter_title="Logs Are For Events, Not User Interface", next_chapter_link="/books/things-i-learnt/outside-project", next_chapter_title="Don't Mess With Things Outside Your Project") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/monitoring", prev_chapter_title="Learn To Monitor", next_chapter_link="/books/things-i-learnt/outside-project", next_chapter_title="Don't Mess With Things Outside Your Project") }}

content/books/things-i-learnt/log-events/index.md

@@ -43,4 +43,4 @@ could have the values to try to figure out why it failed -- surely, logging
 why it failed also helps, but you know what I mean. This is an example of
 something that makes complete sense in logs, but not in user interfaces.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/use-utf8", prev_chapter_title="Always Use UTF-8 For Your Strings", next_chapter_link="/books/things-i-learnt/languages-are-more", next_chapter_title="A Language Is Much More Than A Language") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/use-utf8", prev_chapter_title="Always Use UTF-8 For Your Strings", next_chapter_link="/books/things-i-learnt/monitoring", next_chapter_title=Learn To Monitor"") }}

content/books/things-i-learnt/monitoring/index.md

@@ -0,0 +1,29 @@
++++
+title = "Things I Learnt The Hard Way - Logs Are For Events, Not User Interface"
+date = 2019-07-15
+
+[taxonomies]
+tags = ["en-au", "books", "things i learnt", "monitoring"]
++++
+
+On a previous life, to understand how a system behaved, I added a ton of
+metrics: how fast things were going in, how fast things were going out, how
+many things were in the middle, how many the job processed... Not doing it so
+makes me feel... naked.
+
+<!-- more -->
+
+Monitoring your project performance give you a really good view of how a
+system is behaving. Is the speed going down? Is the system taking longer to
+process an input? Are no inputs being processed?
+
+If you have this kind of information, you can check what is going on in the
+system and understand why. Is it normal? Did a change around the system (the
+other system that produces the input, the system that consumes in the output)
+affected the results?
+
+If you're not measuring, you'll have no idea.
+
+Also, "If you can not measure it, you can not improve it", as Lord Kevin said.
+
+{{ chapters(prev_chapter_link="/books/things-i-learnt/log-events", prev_chapter_title="Logs Are For Events, Not User Interface", next_chapter_link="/books/things-i-learnt/languages-are-more", next_chapter_title="A Language Is Much More Than A Language") }}