Open for Voting

Create component templates or copy existing components

I use the Windows Powershell Script component heavily to extend the reach of Solarwinds.  As an example, I monitor scheduled tasks with a powershell script.  I would like to create an application template that contains multiple instances of my Windows-Powershell-Script-component-based component instead of copying the Powershell script from it into each instance.  Doing it this way means that I have to modify each component by pasting the same script any time I update the logic.  My solution thus far has been to create an application template that contains a single instance of my homebrewed scheduled task monitor and then assign that template to a node multiple times, overriding the script argument with the Scheduled Task name.  This works, but doesn't provide the appropriate logical grouping of multiple scheduled tasks as components of the same application.

  • I've voted up for this one as I think it's a really important feature that's currently missing.

    Moreover as a further development, having the possibility of setting up a central repository for the Script Body part to get the code from, would be extremely useful.

    I've opened the following discussion about it.

    Central Repository for Scripts

  • Agreed.  It's nice that the functionality exists somewhere, but it really does need to be included in the immediate editing commands during a template-editing session.

  • It would be easier if this was available while editing the Template instead of having to exit and go to another view.

  • FormerMember
    FormerMember in reply to aLTeReGo

    The ability to copy components is very useful, but what I'd really like to see is a way to create a new Component Template (or Component Type), which, in my case, would be based on the Windows Powershell script component.  For example, I have a Powershell script component that runs a vbscript identified by a full path -- this allows me to leverage the remote Powershell execution built into SAM to execute a local copy of any .vbs that a developer hands me for monitoring some (potentially weird) application, for example.  It would be great if I could maintain one copy of that script (i.e. the template) and deploy multiple instances of it while changing only the argument supplied to each instance.  That way, if I ever need to modify the script to improve error handling or add some comments, I can do it one time instead of doing it for every deployed copy of that script.

  • It's actually been there since v3.something, but it's new to you. emoticons_happy.png