cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Unmanage reason (like shutdown tracker in Windows 2008)

Unmanage reason (like shutdown tracker in Windows 2008)

I don't want anybody to use unmanage for no reason. Because that's what they are doing for almost every down node! And I have to ask everytime why did hey do it? Then I decided to create a custom property called "Unmanage reason" (name can be different). But because it is not mandatory they always forget (or intentionally) to fill it. So it should be impossible to unmanage a node without filling the unmanage reason at least which should pops up when anyone click the Unmanage button.

These features also should be implemented along with it.

  • There is no way to extend the unmanage time via NPM Web Console. It can be changed with SQL Query Update. But it is not flexible.
  • Unmanage date should be visible on the node details page. I can only see it via reports. (Partially implemented on NPM 10.6 Beta 2)

Also the most needed features in NPM are below (IMHO)

Please vote those ideas as well if you think you need them.

38 Comments
Level 14

Still no answer from SolarWinds.

I meant attention not answer sorry. But thanks for the answer anyway.

And don't forget to vote

Level 11

Hi Mustafa,

Could you tell me how did you create resource below in npm ?

Thanks !

Level 14

Without this ability, I designed a quick work-around. 

1)  I created a custom property called 'Unmanage Reason' and defined a set of reason codes

2)  I created a report that checks for both currently unmanaged nodes as well as nodes that will be unmanaged today.  (Custom SQL reports)

3)  I created an alert that checks for nodes that are unmanaged and do not have a reason code defined.

4)  (To be implemented) I need to create a check for nodes were the unmanage has expired (Nodes.UnmanageUntil) and the unmanage code has not been cleared

It's not a perfect solution, but it does allow me to track our unmanage use and allows us to include the node unmanage as part of our maintenance or troubleshooting process.

Level 13

CAn functionality like this be added to the npm baseline

I don't have time or interest in creating, debugging and maintaining custom SQL code on a third party tool

Level 14

I am starting to think these votes are not so important. This is the top requested feature and yet it's not on the roadmap.

Level 9

This would be great... along with the need of who turned off the alerts.

Level 8

This was my dream, This would be really helpful in TPM.

I'd like to add one more thing to this request:

add a way to attach an email or attach a string of text to the "Reason for unmanaging", when a node is to be unmanaged?

It'd be nice for me to reference the documentation we have when we are unmanaging something.  This would work great for mass-unmanaging, as well as cut down on unnecessary datacenter documentation.

Level 14

I like it.

Level 13

yes, pls add this feature