Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

APM 4 Templates with Same Counters - Data Continuity

SolarWinds has recently released new versions of some of the APM templates for APM 4.0.2. In this particular case, we already had the previous version of the template deployed. So to test the new templates we deployed them alongside the original template on the same host.

In this case we have two Windows File Server Templates deployed. One called "Windows Server 2003-2008" (shipped with APM) and the other called "Windows Server 2003-2008 Services and Counters" (Content Exchange by SolarWinds). Both templates contain the some of the same (duplicated) counters. The new template has additional counters.

Now, we'd like to move to the new templates entirely, but in doing so, all the old data will be gone. Is there a way to move the old data over to the new counters? There doesn't appear to be a way to drag and drop counters from one template to another to retain the data, so I guess it would all need to be done via SQL.

To us, this is a huge issue. When a new version of a template is developed and needs to be deployed, preserving and displaying historical data is crucial. I guess we just expected a data collection to be more intelligent and APM to understand that we already had data in the database for those counters and to continue on from where we left off.

Find more posts tagged with

apm_4.0.2

Accepted answers

Questionario

hey jspanitz,

you could just add all "missing" components to your existing template, apm gives you the option to see all components from templates and then select them and add them to existing templates. that way you would preserve the data

hope it helps

All comments

macnugetz

Thanks for the feedback, John. We are evaluating what we can do in terms of data preservation when moving from an old template to a new one. I will let you know what we come up with.

-Craig

Questionario

hey jspanitz,

hope it helps

jspanitz

I'll give you that is true (points to you!). I guess that is the somewhat good thing about Orion’s flexibility. There is always a workaround.

However, from a customer perspective, it's a real waste of time and resources. And from a technical perspective, we would still like to see APM smart enough to know that we are already collecting that data and to not collect it again.

Questionario

how would it then decide when to not keep the data in case you do want to start fresh? :P

I'd like to see APM working reliably without major bugs first before implementing even more features