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

Unmanage a transaction with API

ckennedy1

Hello,

I currently use the following to unmanage a node from the API.

curl -k -u user: -X POST -H "Content-Type: application/json" -d @unmanage.txt "x:17778/.../Unmanage"

unmanage.txt -

["N:19","04-26-2017 12:00:00 PM","04-27-2017 02:00:00 PM","false"]

I tried using this since transactions have an ID assigned -

["T:2","04-26-2017 12:00:00 PM","04-27-2017 02:00:00 PM","false"]

which returned a clear error -

{"Message":"Only nodes can be unmanaged through this interface. T:2 does not refer to a node.","ExceptionType":"System.NotSupportedException","FullException":"System.NotSupportedException: Only nodes can be unmanaged through this interface. T:2 does not refer to a node.\u000d\u000a at SolarWinds.InformationService.Verb.VerbExecutor.Invoke(Object hostInstance, Object[] parameters)\u000d\u000a at SolarWinds.InformationService.Verb.VerbExecutorContext.Invoke()\u000d\u000a at SolarWinds.InformationService.Core.InformationService.Invoke[T](String entity, String verb, Action`1 setupParameters, Func`2 extractReturnValue)"}19

I then tried referencing the table / modifying the call slightly

curl -k -u user: -X POST -H "Content-Type: application/json" -d @unmanage.txt "x:17778/.../Unmanage"

["T:2","04-26-2017 12:00:00 PM","04-27-2017 02:00:00 PM","false"]

which simply returned 'null'.

Could anyone point me in the right direction on how I can unmanage a transaction through the API?

Find more posts tagged with

Accepted answers

tdanner

Your curl command looks right to me:

curl -k -u user: -X POST -H "Content-Type: application/json" -d @unmanage.txt "https://x:17778/Solarwinds/InformationService/v3/json/Invoke/Orion.SEUM.Transactions/Unmanage"

["T:2","04-26-2017 12:00:00 PM","04-27-2017 02:00:00 PM","false"]

And it did not return an error. Are you saying that the transaction was not in fact unmanaged after doing this?

All comments

stevenwhunt

Have you tried using the Orion SDK?

ckennedy1

I looked at the SDK previously, but for this I would like to use the actual API if possible, without any dependencies.

stevenwhunt

The SDK is the currently recommended methodology for any non UI automation.

ckennedy1

The above method that I posted works perfectly fine for managing / unmanaging nodes through a curl call, so I'm a bit confused as to why transactions wouldn't work in a similar state. As I mentioned, I am attempting this without further dependencies, as sending a payload over the headers is much cleaner than needing to integrate further dependencies across the board. Does the consistency not work across the board between nodes / transactions?

Judging from a previous post - https://thwack.solarwinds.com/thread/59330 - it looks like I am attempting a similar call, except without the SDK. The payload I am passing in the headers appears to be the same thing -

$swis->Invoke("Orion.SEUM.Transactions","Unmanage",["???", $now, $later, "false"]);

If what I am attempting to do isn't possible, please let me know, but I don't think I'm far off.

tdanner

Your curl command looks right to me:

curl -k -u user: -X POST -H "Content-Type: application/json" -d @unmanage.txt "https://x:17778/Solarwinds/InformationService/v3/json/Invoke/Orion.SEUM.Transactions/Unmanage"

["T:2","04-26-2017 12:00:00 PM","04-27-2017 02:00:00 PM","false"]

And it did not return an error. Are you saying that the transaction was not in fact unmanaged after doing this?

ckennedy1

Thanks for confirming, and providing a sanity check. I was looking at the 'Audit Report' on a Node level to see the records go through properly, but this didn't exist on a transaction level so I didn't think it was working. After putting a node into an unmanaged state that was a current time, I was able to see it worked. I then added a table to display the fields from the Transactions table, and all is well. Thanks to both of your for your help with this!