By Ops, for Ops

March 26th, 2013 by

barriersWhen I came into the office this morning, I was greeted by an email requesting some kill points for a competitive product; a product I used to use on a daily basis.  You see I was not always a product manager here at ScienceLogic.  Before joining ScienceLogic, I ran a Network Operations Center (NOC) for a data center and managed service provider.  While running that NOC, I had the opportunity to use and evaluate a lot of IT management tools.  And, it just so happens that we replaced many of them with EM7 and it is still running there today.

Writing my reply to that email reminded me of why I bought the product.  In a nutshell, ScienceLogic understood my business.  They understood my challenges.  They understood IT operations.  EM7 was written for me, well not really for me, but it was written for people just like me; operations people.

Now this is no surprise when you look at the founders of ScienceLogic; all seasoned veterans of IT operations.  But what is surprising is how many other tools out there seemed to miss the mark or better yet they do the job, but require us to deal with some assumption some developer or product manager made along the way that as an operations person I would have never made.

Today during my stroll down memory lane, I was reminded of some of these assumptions.  I once used a product for managing Windows servers that required the same username and password be configured on every server.  Now in an enterprise environment, this is not a problem.  Create a new account, make it a domain administrator and voilà, you are done.  Need to change that password because of a staffing change, just change the domain credential and once again voilà, you are done.  But imagine the challenges something as simple as this would cause for a managed service provider.  There are no domains, or more likely there are hundreds of them.  Using the same username and password for multiple customers? Huh? How is that secure?

Another assumption was that no two servers had the same name.  Once again in an enterprise on a single domain, this is normal.  In fact unique server names are required.  But once we obscure the domain boundaries as we often do as service providers, servers with the same name become quite common.  If memory serves me correctly, we had a least 7 customers all of which had a web server named www.

The bottom line is this: tools need to make your life easier and eliminate the silos and barriers that exist within organizations and departments.  And it just so happens EM7 does exactly that.

Tagged with: , , , ,

Add comment

Leave a Comment

Required

Required, hidden

 

Some HTML allowed:
<a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Trackback this post  |  Subscribe to the comments via RSS Feed


Our blog’s authors aren’t just experts in their field, they’re also key contributors to our world-class monitoring platform. If you’d like to see how these topics play out in a real-world setting, please register for a free, no pressure demo:

Request a demo

Search


type keywords | hit enter

Navigation

Recent Posts

Categories

Archives

Recent Comments

Subscribe