AdatoSystems is committed to helping organizations leverage systems management tools to increase stability, reliability, and value.

In plain English, we:

  • Install, Improve and Integrate monitoring systems and software (Monitoring)
  • Design and Deploy websites (Web Design)
  • Automatically Backup and Update your WordPress website (SiteButler)
  • keep your “IT stuff” running with as little cost and effort as possible

A few of the amazing teams we’ve been privileged to work with can be found on our Customers Page. But the real story is what we can do for YOU.

There is nothing cookie-cutter about your organization, so our approach is anything but. We’ll find out your business goals, your technical challenges, and present you with options on how we can help.

Read More…

Lose, Survive, or Win?

My teenage son has had a rough patch lately – like many teens. Getting up for school requires Herculean commitment. Being civil, let alone kind, is almost impossible.

No surprises there, it’s all part of the journey.

This morning as I drove him to school, I asked him if he was going to let the morning’s bad start ruin the rest of his day.

“Nope” came hims typically verbose reply.
“So,” I asked. “Do you plan to lose, survive, or win?”
“Uh…. survive?” he answered, clearly thrown off his recalcitrant game.
“Interesting choice.” I said, and left it at that.

But I think it’s worth asking ourselves each day. As we prepare to meet the challenges inherent in the day of a typical IT pro, do we envision ourselves losing, surviving, or finding a way to win?

Sometimes it’s not important whether you actually win. Sometimes what matters – on day 463 of your job – what your plan is.

The rest is part of the journey.

MovieBob and Magneto

(Inspired by the article: “Magneto was Right” which has subsequently been taken down, but the video is here)

I really liked the character of Magneto in X-Men 1 and 2. The character had a point and a purpose and an inner consistency. He wasn’t “evil” any more than most of us are, he simply framed things differently than Xavier and acted based on his own values.

It’s like this: The power goes out in my neighborhood and some people think “candle light block party” while others lock the doors in case there’s looting and riots. Neither option is totally far out, it just depends on how you see the world.

Coming back to Bob. I got picked on in school. Most of the people I associated with got picked on too. Depending on the day and context, it was because I was a band geek, or a theater dweeb, or a fashion train wreck, or socially inept, or somehow being “an easy target”.

At least, that’s what I’ve always assumed. And since it was me getting picked on and not me picking on them, I assumed there was a flaw in me that invited the abuse.

But I think MovieBob is truly onto something, and not just because he’s using comic book characters as his foil.

My favorite point:
Bullies pick on us NOT because “we’re different” (MovieBob says “I can attest that they came in all shapes and sizes. A veritable rainbow coalition of torment.”).

NO, the thing we all suspect deep down is that it’s not that we’re different, we’re BETTER.

Bob uses images from Revenge of the Nerds in his discussion, and that might be the most accurate. The narrative of the geeks realizing their own self worth and playing to their strengths may be a fantasy, but it’s definitely a satisfying one as well as one that is actually playing out in reality with more and more frequency.

Breaking the Loop

There are times when doing it all over again can be part of a brand new discovery. And there are times (maybe MOST of the time) when it’s not.

There are times when doing it over is just busywork, repetition, your own little slice of Groundhog Day (but without getting Andie McDowell at the end, or becoming a surgeon, or anything).

Welcome to 80% of the work of IT. Figuring out a solution once and then doing it again and again and…

Hopefully, right about now, you are asking yourself “who would want to do that?”

If a response is known, repeatable, and predictable, shouldn’t it be automated? If a service stops, automatically restart it. If a disk is filling up, clear the temp directory. If the server has too many connections, clear the ones that are old, or stale, or showing no activity.

“But it’s not that simple” you say? Each solution is a snowflake, unique in it’s particulars? That’s fine. NOT repeatable or predictable happens too.

But if you find yourself locked into a circular routine, each ticket blurring into the previous one, it might be time to look for a pattern so you can break out of it.

LINK: Do what you love

And thanks to Doug at http://www.asknice.com for pointing it out.

How to Do What You Love
January 2006

To do something well you have to like it. That idea is not exactly novel. We’ve got it down to four words: “Do what you love.” But it’s not enough just to tell people that. Doing what you love is complicated.

The very idea is foreign to what most of us learn as kids. When I was a kid, it seemed as if work and fun were opposites by definition. Life had two states: some of the time adults were making you do things, and that was called work; the rest of the time you could do what you wanted, and that was called playing. Occasionally the things adults made you do were fun, just as, occasionally, playing wasn’t– for example, if you fell and hurt yourself. But except for these few anomalous cases, work was pretty much defined as not-fun.

And it did not seem to be an accident. School, it was implied, was tedious because it was preparation for grownup work.

The world then was divided into two groups, grownups and kids. Grownups, like some kind of cursed race, had to work. Kids didn’t, but they did have to go to school, which was a dilute version of work meant to prepare us for the real thing. Much as we disliked school, the grownups all agreed that grownup work was worse, and that we had it easy.

Teachers in particular all seemed to believe implicitly that work was not fun. Which is not surprising: work wasn’t fun for most of them. Why did we have to memorize state capitals instead of playing dodge-ball? For the same reason they had to watch over a bunch of kids instead of lying on a beach. You couldn’t just do what you wanted.

I’m not saying we should let little kids do whatever they want. They may have to be made to work on certain things. But if we make kids work on dull stuff, it might be wise to tell them that tediousness is not the defining quality of work, and indeed that the reason they have to work on dull stuff now is so they can work on more interesting stuff later. [1]

Once, when I was about 9 or 10, my father told me I could be whatever I wanted when I grew up, so long as I enjoyed it. I remember that precisely because it seemed so anomalous. It was like being told to use dry water. Whatever I thought he meant, I didn’t think he meant work could literally be fun– fun like playing. It took me years to grasp that.

By high school, the prospect of an actual job was on the horizon. Adults would sometimes come to speak to us about their work, or we would go to see them at work. It was always understood that they enjoyed what they did. In retrospect I think one may have: the private jet pilot. But I don’t think the bank manager really did.

The main reason they all acted as if they enjoyed their work was presumably the upper-middle class convention that you’re supposed to. It would not merely be bad for your career to say that you despised your job, but a social faux-pas.

Why is it conventional to pretend to like what you do? The first sentence of this essay explains that. If you have to like something to do it well, then the most successful people will all like what they do. That’s where the upper-middle class tradition comes from. Just as houses all over America are full of chairs that are, without the owners even knowing it, nth-degree imitations of chairs designed 250 years ago for French kings, conventional attitudes about work are, without the owners even knowing it, nth-degree imitations of the attitudes of people who’ve done great things.

What a recipe for alienation. By the time they reach an age to think about what they’d like to do, most kids have been thoroughly misled about the idea of loving one’s work. School has trained them to regard work as an unpleasant duty. Having a job is said to be even more onerous than schoolwork. And yet all the adults claim to like what they do. You can’t blame kids for thinking “I am not like these people; I am not suited to this world.”

Actually they’ve been told three lies: the stuff they’ve been taught to regard as work in school is not real work; grownup work is not (necessarily) worse than schoolwork; and many of the adults around them are lying when they say they like what they do.

The most dangerous liars can be the kids’ own parents. If you take a boring job to give your family a high standard of living, as so many people do, you risk infecting your kids with the idea that work is boring. [2] Maybe it would be better for kids in this one case if parents were not so unselfish. A parent who set an example of loving their work might help their kids more than an expensive house. [3]

It was not till I was in college that the idea of work finally broke free from the idea of making a living. Then the important question became not how to make money, but what to work on. Ideally these coincided, but some spectacular boundary cases (like Einstein in the patent office) proved they weren’t identical.
… read more here: http://www.paulgraham.com/love.html

I’d Like the Record to Reflect…

What do you do when creativity refuses to cooperate? When you have the intention to create something, but that spark, that “thing” just isn’t happening?

Author Elizabeth Gilbert (“Eat, Pray, Love”) gave a speech about nurturing creativity at the 2009 TED conference. I strongly recommend it to anyone who has 19 minutes to spare:  http://www.ted.com/talks/view/id/453

Near the end of Ms. Gilbert’s talk she speaks to the invisible externalized part of her that provides inspiration:

You and I both know that if this book is not brilliant, that is not entirely my fault, because you can see that I am putting everything I have into this […] so if you want it to be better, then you’re going to have to show up and do your part of the deal […] but if you don’t do that, then […] I’m going to keep writing because *that’s my job*. And I would please like the record to reflect today that *I* showed up for my part of the job.

As I.T. professionals, we don’t always think of ourselves as particularly “creative”. But if we are honest, we know there are moments. We actually seek them out.

When I.T. pros connect with their creative selves, “just fixing it” turns into a solution which is elegant, inspired, and repeatable.

Don’t Tell Me “It’s Complicated”

HT to my hero and writing inspiration Seth Godin. His post here got me started, and his style is something I have wanted to emulate for years now.


don’t tell me that it – monitoring – is complicated.

Don’t tell me you’re a snowflake – unique in your need for 1200 alert rules.

Don’t tell me “but our company is different. WE create value for our shareholders. Not like your other clients.”

Don’t tell me you can’t do it because…


I’ve been creating monitoring solutions for over a decade.

I’ve designed solutions that scaled to 250,000 systems, in 5,000 locations

I work at a company that has written millions of lines of code to do this one thing, and do it well.

So please Don’t tell me it’s complicated.

Tell me what you need. What you want. What you wish you could have.

And then LISTEN to what I have to say. Because I’ve seen this before. I’ve done this before. And it’s NOT complicated. It’s also not easy.

But it is simple.

Colored Perceptions

I will freely admit up-front that I know little, if anything about businesses, startups or even management – except for the kinds of work environments and management styles I prefer to be an employee of/in/for.

Having said that, Bob Lewis’ recent article on the Phoenix principal (http://www.weblog.keepthejointrunning.com/wordpress/?p=2972) reminded me of Crayola.

In my mind, when thinking about how successful a company can be in the future, the starting point is “what do they do?” – well, “everyone knows” Crayola makes crayons. Everyone knows that.

[note: when reading over this, my wife quickly pointed out that “everyone” is obviously people who don’t spend a lot of time being with or shopping for kids. Because what I discovered below is pretty common knowledge in her circle of associates. As always, YMMV.]

As far as product diversity, my assumption was that their product line would include different sized boxes of crayons, and that they’ve branched out into washable markers. I figured they probably get some revenue from supplying those small 3- or 4-crayon packs to restaurants. After that, there’s not much to say, right?

Take one look at their web site though, and the whole theory is blown out of the water. This isn’t a crayon company. This isn’t even an art-supply company.

From what I can see, Crayola sells artistic inspiration, and it’s target consumer group is one which universally – to the last person – believes they are imminently talented artists. Kids.

The Crayola web site is completely focused on encouraging visitors to be artistic. There are coloring pages. Lesson plans for teachers. An e-card creator. An online calendar that lists events like National Wildflower week (May 4-8), International Museum day (May 18) and the Dragon Boat festival in china (May 28).

This point was driven home (hah!) when my wife showed me a sidewalk paint foam sprayer she bought for my son’s birthday.

A Sprayer. For paint. That foams. On your driveway.

That’s about as far from waxy crayons as you can get and still be in the same solar system.

Maybe I’m lionizing them and this is just good business (again, I’m not a business guy so I could be overly impressed by nothing). But it seems to be that this is a company that is thinking hard about their essential mission, and choosing not to be stopped by artificial boundaries with regard to “this is what we make”.

Someone once told me that Cisco bills itself (internally at least) as a software company. Not hardware, that’s just a means to an end, which is delivering the IOS (among other things) to customers. I have a few friends in Cisco now, and I’m not sure that’s really the case. But at the time it struck me as a novel way for them to look at themselves.

This realization has, in turn, made me think hard about what my mission is – in life, in business, in my usual work day. Do I really just fix computer problems? Is there (or could there be) something more noble to this, a higher purpose which would inform my choices?

I’m sure a lot of people may see this as a cynical exercise in re-branding – doing the same thing but calling it something different. But this has to be more than billing myself as “a sanitation engineer” instead of a garbage collector. This needs to be a change in focus and philosophy, or else it will be easily detected for what it is – a cheap marketing ploy.

So that’s it, my big idea for the week. I think I’m going to go crack open that package of glow-in-the-dark finger paints and see what kind of mess I can make.

Showing Your Scars

One summer I was hired to help build scenery for a local summer stock theater venue. The problem is that I had been trained as an electrician, so every task in the wood shop required that I learn new skills on-the-fly. Because this was a job not a class and I was expected to know what I was doing, I didn’t ask enough questions and ended up making about twice as many mistakes as necessary on everything. Most of those mistakes weren’t life-threatening.

But one of the times, I was working on the table saw had my first experience with kick-back (for a video of what this looks like, see here. No, that’s not me.).

Similar to the video linked above, I was lucky that nobody was hurt, but then something weird happened – everyone started showing off their scars.

Guys who hadn’t even been in the wood shop when my accident happened came down from ladders, up from trenches, and over from across the park to show me scars that decorated their arms, fingers, hands, legs, and torsos. Each one came with a story, and the stories were remarkably similar:

“I was doing this thing… I was standing in the wrong place… I stopped paying attention for a second…  and BOOM!”

This story was followed by “And that’s why from then on I always make sure I <fill in the name of the safety procedure>”.

In addition to being thankful that no one was harmed, I was grateful for them not making me feel like I was a complete numskull for letting this happen. Apparently it can (and does) happen to everyone.

But I also wondered why nobody thought to tell those stories on the FIRST day. Like I said earlier, this wasn’t a teaching environment but I could imagine some sort of first-day ritual – the showing of the scars – where everyone lists their  experiences (in effect, showing their scars) and sharing the life lessons they learned from them.

Because not EVERYONE has had EVERY mishap, but in a team of 5 or more professionals, collectively the group has seen a lot.

At the time I thought that if every scene shop adopted a custom like that, more people would learn better lessons and have fewer scars (not to mention more severe injuries) to show for it.

I was reminded of this episode in my life the other day, when someone tweeted about reconfiguring a remote network device, only to find they had messed up one of the commands and the entire site was no longer accessible. A 2 hour drive was required to get on-site and fix the issue.

Immediately after the tweet came an outpouring of advice:

“Cisco’s ‘reload in’ command is your best friend.”;
“Always test your config in GNS3 first”;
“Never update a config until another set of eyes has looked at it first”
…and so on…

It reminded me of everyone coming down to the scene shop to show me their scars.

The next time you are sitting with your colleagues at the office – maybe you have a new face on the team; or maybe it’s YOUR first day; or maybe you’re starting a new project. Think about ways you can initiate a “showing of the scars”. Go around the table and list out your worst mistakes and the lessons you learned from them.

I’m willing to bet that you will grow closer as a team; that fewer “rookie” mistakes will be made by everyone; and that even the most grizzled veterans will probably learn a few things they didn’t know (or possibly had forgotten).

More people learning better lessons with fewer scars to show for it.

Using NetFlow monitoring tactics to solve bandwidth mysteries

NetFlow eliminated the hassle of network troubleshooting after a school complained about its Internet access.

Life in IT can be pretty entertaining. And apparently we admins aren’t the only ones who think so — Hollywood’s taken notice, too. The problem is, the television shows and feature films about IT are all comedies. I’m not saying we don’t experience some pretty humorous stuff, but I want a real show; you know, something with substance. I can see it now — The Xmit (and RCV) Files: The Truth is Out There.

 In fact, I’ve already got the pilot episode all planned. It’s based on an experience I had not long ago with the NetFlow monitoring protocol.

The company I was with at the time offered monitoring as a service to a variety of clients. One day, I was holding the receiver away from my head as a school principal shouted, “The Internet keeps going down! You’ve got to do something.”

Now, there are few phrases that get my goat like “the Internet is down,” or its more common cousin, “the network is down.” So, my first thought was, “Buddy, we have redundant circuits, switches configured for failover and comprehensive monitoring. The network is not down, so please shut up.”

Of course, that’s not what I said. Instead, I asked a few questions that would help me narrow down the root cause of the problem.

First up: “How often are you experiencing this issue?”

“A bunch,” I was told.

“Ooookay … at any particular time?” I asked.

He replied, “Well, it seems kind of random.”

Gee, thanks. I’m sure I can figure it out with such insightful detail.

It was obvious I was going to have to do some real investigation. My first check was the primary circuit to our provider. Nothing there. So, I’m sorry, Virginia, but “the Internet” is not down, as if I had any doubt.

Next, I looked at the school’s WAN interface, which revealed that yes indeed, the WAN link to the school was becoming saturated at various intervals during the day. Usage would spike for 20 to 30 minutes, then drop down until the next incident. I checked the firewall logs — not my favorite job, which showed a high volume of http connections at the same times.

Now, for many years, checking was the pinnacle of network troubleshooting — check the devices, check the logs, wait for the event to happen again, dig a little further. And in my case, that might have been all I could do. Our contract had us monitoring the entire core data center for the school system, but that only extended to the edge router for the school. We had exactly zero visibility beyond each individual school building’s WAN connection.

But as chance would have it, I had one more trick up my sleeve: NetFlow.

NetFlow has been around a while, but it’s been only in the last few years that it’s entered the common network admin lexicon, largely due to the maturation of tools that can reliably and meaningfully collect and display NetFlow data. NetFlow collects and correlates “conversations” between two devices as the data passes through a router. You don’t have to monitor the specific endpoints in the conversation, you just have to get data from one router that sits between the two points.


Hmm, that sounds a lot like a WAN router connected to the Internet provider, which is exactly what I had. Correlating the spike times from our bandwidth stats, we saw that during the same period, 10 MAC addresses were starting conversations with YouTube. Every time there was a spike, it was the same set of MAC addresses.

Now, if we had been monitoring inside the school, we could have gleaned much more information — IP address, location, maybe even username if we had some of the more sophisticated user device tracking tools in place — but we weren’t. However, a visit to WireShark’s OUI Lookup Tool revealed that all 10 of those MAC addresses were from — and please forgive the irony — Apple Inc.

At that point, I had exhausted all of the tools at my disposal. So, I called the principal back and gave him the start and stop times of the spikes, along with the information about 10 Apple products being to blame.

“Wait, what time was that?” he asked.

I repeated the times.

“Oh, for the love of … I know what the problem is.” Click.

It turns out the art teacher had been awarded a grant for 10 shiny new iPads. He would go from room to room during art period handing them out and teaching kids how to do video mashups.

This was one of those rare times when a bandwidth increase really was warranted, and after the school’s WAN circuit was reprovisioned, the Internet stopped mysteriously “going down.”

The episode would close with the handsome and sophisticated admin — played by yours truly, of course — looking into the camera and while channeling the great Fox Mulder saying, “Remember, my fellow admins, the truth is out there.” (And, I would add, for those of you reading this blog post, don’t forget how valuable NetFlow can be in finding network truth.)

Now, if that’s not compelling TV, I don’t know what is.

(This article originally appeared on SearchNetworking)