Tag Archives: monitoring

Links: Jun 3

Writing is nature’s way of telling you how sloppy your thinking is.

 Technology:

  • Shocking post-mortem from Joyent: operator mistake and a tool which reboots the whole datacenter without requesting additional confirmation.
  • Defensive BASH programming — an excellent post on scripting techniques!
  • Thinking for programmers by Leslie Lamport. The epigraph comes from this talk.
  • The best expect script I found to execute commands on servers remotely via ssh. This is really handy when one does not have key-based authentication set up. The downside is that it’s slow, so one need to parallelise it if one has over few dozen of servers to crawl.
  • ncf — CFEngine framework for small installations, runs in pure CFEngine language, to help structure your CFEngine policy and provide reusable, single purpose components distributed under the GPLv3 license.
  • The same guys are behind the Rudder — web-driven, role-based solution for IT Infrastructure Automation & Compliance.
  • “Law of Murphy for devops: if thing can able go wrong, is mean is already wrong but you not have Nagios alert of it yet”. Therefore, don’t forget to monitor these things.
  • Interesting stats on monitoring tools — Nagios is the king, Sensu and Zabbix have a large chunk of large deployments.

English:

  • Hilarious story about why programming sucks. Careful and exact observations put in a lively and funny language. It definitely made my day!
  • Quirks with pronunciation of some borrowed words:

    Another word that the British Anglicized from French is harass and its related noun harassment. They shifted the accent to the first syllable, sounding like “harris.” The Americans preferred the French-style second-syllable stress, no doubt further encouraged by the double s. But the British style is becoming more popular with people who don’t want to sound like they’re saying “her ass” — sort of like how the British “urine-us” pronunciation of Uranus, based on the Latin and Greek stress pattern, is sometimes preferred by Americans who don’t like how the American say-it-like-it-looks version sounds like “your anus.”

  • Stop new wordage? Never gonna happen. In defence of unnecessary words.
  • Corporate speak — speaking strategically without a strategy.

As languages go, English is particularly extreme in differentiating between stressed and unstressed syllables; the stressed syllables play a disproportionately big role in making words identifiable, and because unstressed syllables are out of the spotlight, and don’t contribute much to the exact identity of words, it doesn’t really matter exactly what they sound like. For example, some people pronounce the first syllable of believe as /bɪ/, others as /bə/, and in fact it would often be hard to tell exactly which vowel sound is used. Even if you use a different one – if you say, for example, /bʊ/ or /be/ – the identity of the word will be clear; the important thing is to pronounce the stressed second syllable with a clear /iː/ vowel.

— http://www.macmillandictionaryblog.com/schwa-syllables-and-words-in-different-guises-part-1

Other:

The story behind lavabit shut down.




Links: Feb 16

Change of plan! Will now try to write shorter posts but more often. With bigger posts, if I miss a date, they start to scare me off writing them as I know that would require substantial time investment.

Recently I have discovered how once never-failing task prioritisation strategy can backfire. You most certainly know the strategy: an interesting, engaging, and enjoyable task should be stashed and used as a treat after one sorts out boring or urgent assignments.

You’d wonder how this could possibly go wrong? Here’s what happened with me: one of the tasks, which I long wanted to implement myself, was finally approved and assigned to me with low priority. I revelled and carefully set it aside so I could come back to it with enough time to do it neat and proper. Alas! For the next three (!) weeks, due to routine, urgent, and other business, I haven’t got enough time to tackle it.

Eventually, the task received medium priority and I had to implement it within certain time constraints. This obviously meant it wasn’t as neat as I wanted it to be; this also meant it wasn’t a treat anymore! Broken hopes and bad mood instead of delight and satisfaction! Horrible experience, beware. Now I’m trying to get back to it and rework the way I would at least be content with.

Okay, let’s shove in some of the interesting links I came across last month:

Other:

Tom Limoncelli referred an interesting article that defines five stages of how management, owners, and investors treat IT in their businesses:

  1. Cost center
  2. Service Provider
  3. IT Partner
  4. Business Peer
  5. Business Game Changer

Implication is the further stage you’re in, the better it is. It struck me though that some firms actually may advance in a backward direction! I would not want to stay with the firm that made more than one step backwards (one step might be a coincidence, two — a pattern).

Why would someone writing in Python and Ruby want to learn Java? Here’s an explanation: Why I’m Learning Java.

Technology:

    • Valuable bookmark: how to count and quantify the number of syscalls a program makes? Here’s an example using SystemTap.
    • Very good explanation why systemd raises so many questions and fires heated debate — systemd: broken by design.
    • Vector — an interesting tool for predictive scaling and flexible downscaling of your AWS environments.
    • Blockade — a utility for testing network failures and partitions in distributed applications.
    • Provocatively titled post ‘10 things we forgot to monitor‘ lists some of the things you shouldn’t be missing in your monitoring. Included mostly for scripts examples.
    • Flapjack — monitoring notification routing + event processing system. More details on how and why and a live demo.
    • Very expressive presentation on how to build a modern monitoring subsystem:


 

 

English


Seems I’ve failed to make this post short. Have so many interesting things in my drafts that it’s challenging to stop once started. Will improve next time. That’ll be all for today, folks.