Comments
-
I agree wholeheartedly. In addition, there should be a similar process to do simple checks on the health of the database. If I'm on a 5 minute polling interval and don't have any data for the past 18 hours, there is something wrong. We have implemented a check along these lines in APM, but it suffers from the same problem…
-
I would vote for this 100 times if I could.
-
Oddly enough, the copy I was working with did not have the trailing slashes... I wonder if I removed them sometime last week while messing around with this. Commenting the namespace and forcing the query element into the proper namespace did the trick. Thank you very much for your help! This will help us out immensely once…
-
unfortunately my company doesn't allow us to have administrative privileges on our corporate laptops, so fiddler is most likely unable to be used. I have been attempting to load the wsdl in soapui, and keep getting this error: 2011-10-12 10:46:57,616 ERROR [errorlog]…
-
I fixed the namespaces and it does not seem to have helped. here is the script itself. It is followed by the testAPIPackage.pm that contains the InformationService package definition. It would require an account named 'test' with password 'testing'. I have replaced our actual server ip with 192.168.0.1. This requires at…
-
This is a request we would be incredibly interested in as well.
-
I accidentally delete a > when editing that for readability...
-
VideoPropulsion Floodgate 1.3.6.1.4.1.25864.1.1, I think. might not need the last .1.1
-
Figured out how to avoid the 'gensym' naming, but it doesn't seem to have helped. Here's the newly generated Envelope: <?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:wsu="">docs.oasis-open.org/.../oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap12="">schemas.xmlsoap.org/.../"…
-
I've used SOAP::Lite to generate a package "InformationService" from the wsdl. I create an object of this package, set the appropriate SSL/authorization parameters and call the 'QueryXml' method on the informationservice object, passing the string to it. I will play around with it a bit to see if I can affect how it…
-
Doh! I fixed the typo, but have the same response. I checked the log you indicated, but the only entry was from a bad call using SWQL Studio while attempting to figure out what the problem might be.
-
The only thing I've been testing so far is adding and deleting nodes and interfaces, so the only operation I would have expected to see audit events for that I'm not is adding nodes. Are there supposed to be audit events for adding/removing interfaces? If so, I'm not seeing those either. It may or may not matter, but we…
-
That's fine if that's the case, as far as pulling interface statistics. I'd still be interested if there is a way to get it to show up as something other than "Unknown."
-
As do I. @Byrona: Neverending Story. Nice!
-
DOH! the account limitations - i was using a 'test' account and had forgotten that we had placed limitations on it for other testing. thank you very much and apologies for the silly question :)
-
That fixed it. If it helps, while attempting to troubleshoot, I also tried using interfaceName and added interfaceIndex... and ran into the same issue.
-
nope. it's the little things..... fixed. thank you again.
-
To clarify... are you wanting additional levels of grouping? Although it's a little cumbersome, you could add a custom property ("company," for example) to your NPM installation, then set that property based on each company. Then you add a second (and/or third) "All Nodes Tree" resource to the summary view you are using,…
-
I think I've figured out a part of why this was difficult to understand at first. In the .pm module, I edited the 'parameters' entry of the 'QueryXml' method as such: parameters => [ SOAP::Data->new(name => 'query', type => 'xsd:string', attr => {xmlns=>'http://schemas.solarwinds.com/2007/08/informationservice'}), ], # end…
-
After fiddling with it some more, I think I've bypassed whatever my previous problem was. However, I've hit a new snag. I'm getting response code 400 "Bad Request". The 'soapAction' is now pointed at "">schemas.solarwinds.com/.../QueryXml" and it is still connecting to 'https://(my server…
-
If it helps, here is the 'content' of the message, which is being sent to https://(my server here):17778/SolarWinds/InformationService/OrionBasic, with the 'soapaction' header set to "#QueryXml"... <?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:xsi="">www.w3.org/.../XMLSchema-instance"…
-
I see this from May indicating there is a bug specifically with custom property changes. With my current testing, we seem to be getting audit events for deleting nodes and _only_ for deleting nodes. Has there been any followup on that?
-
I would like to add another voice to the request for an audit trail. One thing I would love to see is more granular and well-built permissions. If I give someone access to manage accounts, they should be able to do all tasks involved therin - including managing the limitations on the account - instead of also having to…
