The up.time IT Systems Management Blog

Posts Tagged ‘Windows Monitoring’

Stop the IT “Blame Game” and Get a Single Source of Truth!

Friday, February 22nd, 2013

My landlord just kicked me out.  Let me rephrase that.  My landlord just politely asked me to leave his property before my lease is up.  Thanks to him, my wife and I have been packing our stuff in preparation of our move.  In all honesty, my wife has been doing most of the packing.  I asked her to pack up all her belongings and kitchenware and I would do the rest.  Somehow, that message got lost and she packed my things too.  When I needed to look for my shoes and  couldn’t find them, I was upset.  I reiterated how I asked her to only pack her stuff but she said I never said her that.  Before I knew it, the blame game was in full effect.  It was her word versus mine.

These kind of things happen in IT infrastructure management too.  When you have more than one tool to monitor your environment and more than one data source for capacity planning, how do you know which one to trust?  The justification for IT environments to use a variety of monitoring tools is that their current set of tools cannot provide all the visibility they need.  For example, some tools are strictly for network monitoring.  Others might go really deep in Windows monitoring but light on everything else.  What’s worse is if there is an overlap in the metrics from each tool, so which one should you go with?  Different tools will gather metrics in different ways and at different time intervals.  One tool might catch a spike while another may not.  It is a full time job just to consolidate data and close information gaps to make sense of it all.

Here is where up.time is different.  up.time provides unified monitoring for all the silos within an IT infrastructure so you can have a true ‘single pane of glass’.  You don’t have to duct tape point tools together to make a homemade Swiss army knife.  up.time IS the swiss army knife and provides a unified and comprehensive view.  It makes capacity planning a breeze because it provides a single data source so you don’t have to try to make sense all the differing metrics!  You can eliminate the blame game (and headaches) in IT when you don’t have multiple tools telling you different things.  You don’t have to go to war with the network team arguing whose data is right when you have a standard tool providing a single view of the truth.  up.time is the solution that enables you to be the IT superstar.  Download up.time and give it a spin today!

Constantly Improving… New features in up.time

Monday, September 20th, 2010

For today’s blog I thought I’d talk a little about a couple small features that came in the latest version of up.time. Specifically I want to talk about the Windows agent/agent-less monitoring and service groups.

I’ve already talked enough on the agent vs. agent-less Windows stuff, but there may be a feature most people are not familiar with. Once you add a Windows agent or agent-less system to up.time, it is not locked down to that protocol; you can convert them. For example, let’s say originally we added all our Windows systems to up.time as agent systems. We can keep them as they are and not make any changes, or we can actually convert these systems to use the Windows agent-less (WMI) method. Where and how? Glad you asked.

Your up.time “superadmin” user can login and click on the “Config” tab at the top and go to the “Bulk Element Conversion” section. Here they will be able to select their Windows systems and convert them to/from agent/agent-less. Before you can do this though, just go to the link above it named “Global Element Settings” so you can specify the default settings that will be used for the conversion, such as what default uptime port (9998) and/or the default user/pass for WMI authenticated user. Then you can freely convert to/from agent and agent-less collection methods with a simple click.

The other little-known feature is in our service groups capability. You could always detach a service from a service group if you wanted to make an exception, but the problem was that it was a confusing process to “re-attach”. Once a service was detached from a service group, the only way to get it synced up again was to delete the service, remove the system from the service group, and then re-add the system. This would cause all the monitor(s) to be re-created for that system. You can see how this might be confusing.

Now, when you detach a service from a service group, you get a “re-attach service” button that appears and does just that. This makes managing exceptions and undo-ing accidental service detachment super easy and flexible, and these are just some of the little things we’re constantly improving. Next time I think I’ll talk a little about how our MDC (Multi-DataCenter) functionality actually works.

Agent-less Windows Monitoring: No more RDC

Monday, August 16th, 2010

Video - Agentless Wi  <a href=Since my last post I talked about some of the benefits of our new NetFlow capabilities I think this time I’ll talk a little about what’s so great about our new Windows agentless monitoring.

For those who may not be familiar with how agentless Windows monitoring works, it allows us to monitor Windows platforms without the need to install an agent on them first. This means that as soon as you download and install up.time you can add your Windows infrastructure into up.time right away.

It works by using the WMI (Windows Management Instrumentation) interface that is built into Windows to retrieve system performance metrics. So whether you choose to install a Windows agent or monitor a server agent-lessly (via WMI) up.time will still collect the exact same metrics and all of the agent-specific monitors have been updated to work with both an agent or agent-less.

So what does it all mean? Basically we have more flexibility in how we can monitor our Windows infrastructure without making any sacrifices at all. No more using RDC (Remote Desktop Connection) to every Windows server just to quickly install an agent, or setting up an Active Directory group policy to push the agents out to your servers. This is just one more way how up.time helps you utilize your resources more efficiently.

If you’d like to see how this looks in more detail have a look at our 2 minute video on Windows Agentless Monitoring.