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

APM Component Management Problems

Today I ran into an interesting problem with APM when it comes to managing components and I am hoping that there is a better way on the horizon...

I created an Application Template
I scanned all of my nodes for that template using three different possible credential sets
I then realized I wanted to add a new Performance Counter component to the the template
I found the Performance Counter and added it to the template which then automatically applied it to all of my systems where that template had been assigned

Problem: Most of the new components stated failing because they were not using the proper credentials and the only way to update them was to go through and edit each application overriding the template and setting it to use the appropriate credentials like the rest of the components in the application.

Possible Solution: Make it possible to assign a set of credentials to a node. Then in the template you can say Inherit from Node and in the application you can say Inherit from Template. In this case it would have automatically used the correct credentials and would add yet another layer of broad management options.

Thoughts?

Find more posts tagged with

Accepted answers

All comments

qle

Your Inherit from Node suggestion is really a variation on the existing Inherit from Template implementation but from a different perspective. However, your suggestion does beg the question, why was APM implemented with the Inherit from Template feature from the start. It actually makes sense to inherit the credentials from the node most, if not all, of the time. Therefore, my suggestion would be to replace the Inherit from Template option with the Inherit from Node option.

Of course, the credentials library would have to be made over so that you could assign credential sets en masse very much like assigning APM templates today.

The ultimate question to SolarWinds would be whether this "update" to APM would provide enough value to pursue this task.

byrona

Well, what I can say right now is that the current implementation is causing me a LOT of extra work every time I need to add a new process to an application template.

byrona

Your Inherit from Node suggestion is really a variation on the existing Inherit from Template implementation but from a different perspective. However, your suggestion does beg the question, why was APM implemented with the Inherit from Template feature from the start. It actually makes sense to inherit the credentials from the node most, if not all, of the time. Therefore, my suggestion would be to replace the Inherit from Template option with the Inherit from Node option.
Of course, the credentials library would have to be made over so that you could assign credential sets en masse very much like assigning APM templates today.
The ultimate question to SolarWinds would be whether this "update" to APM would provide enough value to pursue this task.

I would agree that having credentials associated with a node versus a template would be preferable. It would certainly solve the problem that I am experiencing.

In the mean time, having APM scan for applications using different sets of permissions is pretty much pointless if you ever plan to add components to those applications later.

ChrystalT

We ran into a similar problem today with APM. I agree that there should be a way to update en masse the APM credentials. It would be nice to see the option to edit multiple assigned templates and assign a set of credentials to all of the selected nodes rather than having to change them one by one. We were forced to change them one at a time today for about 300+ templates for a customer, so what has the possibility with mass edit to take only maybe 20-30 minutes took about 2-3 hours. Please take this feature into consideration for the next release.

Thanks.

Petr.Vilem

There can be more types of component on one application template requiring different credentials even for same node (for some probes you may need windows credentials, for other SQL credentials etc.), so the "inherit from node" option probably would not be so easy to design.

aLTeReGo

here should be a way to update en masse the APM credentials. It would be nice to see the option to edit multiple assigned templates and assign a set of credentials to all of the selected nodes rather than having to change them one by one.

We will consider this for a future release of APM.