Monitoring theory, from scratch — The definitions

Monitoring — it’s not rocket science! Except when it actually is…

The raw and basic definition

  • Monitoring is about observing.
Is this monitoring? Or is it simply a random, unrelated stock photo?
  • Monitoring is about observing things important to your business.
  • Monitoring is about efficiently and promptly observing things important to your business

From monitoring to good tech monitoring

  • Good monitoring is monitoring which allows a human to derive insights about your business’s operation, in order to prevent or minimize damage.
  • It could do things it wasn’t supposed to do, or fail to do the things it was. Let’s call this one ‘correctness’.
  • Maybe it’s trying to do the right things, but does not meet the service level it’s supposed to, like being too slow. I’d like to call this one ‘smoothness’, based on the expected experience.
  • Maybe it’s doing the right things smoothly, but costing us too much money while doing so. Most businesses like to earn money eventually and don’t operate on an infinite budget. I’d like to call this one ‘efficiency’.
  • Another important bit which is unfortunately often neglected, is keeping in trust. A system really should be secure. I’d like to vote for ‘security’.
  • And, while optional for some, abiding by the law that governs your business should be in. Let’s throw in ‘compliance’.
Is this a problem? Or is it simply a random, vaguely related meme template?

Summary/takeaways

  • Monitoring is about efficiently and promptly observing things important to your business
  • Good monitoring is monitoring that allows a human to derive insights about your business’ operation, in order to prevent or minimize damage.
  • Good tech monitoring is monitoring that allows a human to ensure your business operates correctly, smoothly, efficiently, securely and in compliance while reducing false positives and false negatives to a minimum.

--

--

--

A Gil, of all trades. DevOps roles are often called “a one man show”. As it turns out, I’m not a man and never was. Welcome to this one (trans) woman show.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Data Lifecycle management

Key Tips for Successful Agile Web Development

To BEM or not to BEM : Razvan Spatariu

Ask a LOT of questions (Brainstorm)

Exception handling

CSRF DOUBLE SUBMIT COOKIE PATTERN

8 Interesting Facts About Python Programming Language

We Generated P5-Code Based on Text Inputs with OpenAI’s GPT-3 and This Could Show the Future of…

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Gil Bahat (she/her)

Gil Bahat (she/her)

A Gil, of all trades. DevOps roles are often called “a one man show”. As it turns out, I’m not a man and never was. Welcome to this one (trans) woman show.

More from Medium

Kubernetes Multiple Watches Using Threads in Python

Explanations of SSH config for connecting to GCP

Three-tier & multi-layer architecture using Raspberry Pi, Docker containers, Python and OCI/AWS

Working with dynamically created USB devices in Docker