Blog, Events & Press

15 Oct

4 Tips for Avoiding Disruption When Migrating to a New Monitoring Platform

Seagulls flying in the sky

The time has come to transition from one infrastructure monitoring platform to another.

This may seem overwhelming, but it doesn't have to be. Here are four things IT teams can do to better prepare for a smooth transition to a new monitoring platform.

1. Take inventory of what you have in your current system.

Moving from one monitoring system to the next is a lot like moving from one house to another. Now is the time to really go through and take inventory of what you have, what will come with you, what you might need for the new house, and what old junk won't survive the move.

Moving from one monitoring platform to another isn't all that much different. You probably have all kinds of stuff monitored in your current environment that is likely at the brink of retirement, already shut off, or collecting dust somewhere and simply no longer relevant. By the same token, you may need to think about how you're going to implement some new use cases that your modern monitoring platform will be able to facilitate.

2. Train users before you turn over the reigns.

We are all human. We are creatures of habit and we get used to doing things a certain way. Changing monitoring platforms is like changing computer operating systems. Have you ever switched from a Mac to Windows? If so, you are probably familiar with the "Oh, but I used to do it this way" mentality that comes with being an expert in one system before needing to adapt to a new one.

This transition can be hard, but it doesn't have to be unnecessarily complicated. Don't restrict users from educating themselves ahead of time.

3. Run in parallel for a while.

Most technologists find it extremely useful to avoid hot-cuts, where the company shuts off the old system as soon as it feels the new one is ready to go. What if you missed something? What if there is an unexpected operational issue with the new system?

There is usually very little downside to running dual installations for some time. Only if you've had users on the new system for three to six month and everything is working as planned, should you consider shutting off the old system.

You can selectively disable user access to the old system over time, narrowing the user base that can reach the old system. Eventually, only administrators should be able to get into the old platform. If anyone needs something they can't find in the new system, you can always give them access again. Then, make sure whatever they were looking for is covered in the new system and/or educate them on where to find it.

4. Immerse yourself in the new system.

With great power comes great responsibility. You really need to take the time and energy to immerse yourself into the new system. Setting up and transitioning to a new system of such breath and reach requires a few months of solid work. The more of an expert you become, the easier it will be for you to answer user questions and assist with everyday tasks.

For more on infrastructure monitoring, download our free whitepaper, Six Steps to an Effective Performance Monitoring Strategy.

Written by Manuel Harnisch
Director of Platform Services, SevOne

Manuel Harnisch is the Director of Platform Services at SevOne. For more than 15 years, Harnisch has provided strategic leadership, implementation and support for core technology infrastructures.

Subscribe To Our Blog