dwaynekvw

its ridiculous Solarwinds expects you to manually select volumes on each node. do their customers only have a few dozen servers? once you hit the thousands, doing this level of manual micromanagement is just ridiculous for a program that's supposed to monitor servers in the thousands.

ok channel timed out is a separate problem caused by the default query being too big (it was doing a SELECT TOP 1000). when i lowered the number to SELECT TOP 100, it worked. so uninstalling and reinstalling resolved this issue.

nvm, figured it out, my query for some reason was too big for swql studio to handle. my query was "SELECT TOP 1000" and it was hanging. when i tried limiting the results to 100, it worked.

i uninstalled and reinstalled and now get a different error message: :

nope it failed to connect when i specify a port. the strange thing is that it connects fine without specifying a port but isn't able to execute a query after successfully connecting to it

thing is i am running the latest version

omg you are da man, tdanner!! that was absolutely it! the agent record still existed so readding the new agent did not add the node! once i deleted the agent id record from Orion.AgentManagement.Agent, removed the agent and reinstalled it, the node was successfully readded!! the reason for this lil exercise is that i'm…

i've read through both links and see no references on how to discover or add disk volumes.

oh you're right, how silly of me. worked fine after i corrected the misspelling.

that is exactly right!

thanks! that worked beautifully.

i did a similar curl delete: curl -k -u <user>:<pwd> -X DELETE -v https://orion:17778/SolarWinds/InformationService/v3/Json/swis://orion/Orion/Orion.Nodes/NodeID=2215 and it successfully deleted the node (its a rhel 7 vm) but now i cant readd the node back. i usually install the linux agent and it will appear in Orion but…

so our snmp ports are currently closed and we've been installing the orion agent software on our linux servers. from what i see the discovery api uses snmp. is there a way to use the discovery api to interact with the agent software?

i resolved the problem myself. the issue was the orion_engine_id was wrong. managed to find out from some other forum post that i had to check the Orion.Engines node to see what was the appropriate engine id which brings me to an important point about the orion sdk link. the sample scripts provided have ZERO explanation on…