tdanner ✭✭✭✭✭

Ok, it looks like you had the version of the AppMon schema where all of the statistics were in one table instead of being split into three and joined up with a view. To get rid of the residue in advanced alerts (and reports), delete the Applications.* files in the Schemas subdirectory of Program Files\SolarWinds\Orion.

No ConfigurationWizard.log file? Have you run the configuration wizard?

It has not yet been implemented. Asking on thwack is a reasonable way to check up on the status of feature requests. You can also ask in the forum. The product manager for IPAM, reads everything there, and he's the one who decides what features go in a release. I'll let him know that you and Joel below are both very…

The interface type numbers come from IANA. You can see them here: https://www.iana.org/assignments/ianaiftype-mib/ianaiftype-mib

Using the Create/Orion.Nodes API, you need to add the "N.HardwareHealthMonitoring.SNMP.NPM.Cisco" poller type and also one more thing: Add an entry in Orion.NodeSettings with NodeID = {your node id}, SettingName = "NeedsInventory", and SettingValue = "HWH" (for "hardware health"). I added this to the sample here:…

500 usually means an unhandled exception in the website code. If you look at \inetpub\solarwinds\OrionWeb.log you should see the exception message and stack trace. If you post that here I can help you figure out what's causing it.

I don't know of any other cases like this in 8.5.

The API requires an end time, but you can set it quite far in the future if you want. [DateTime]::UtcNow.AddYears(10) will work fine. Then just call Remanage when patching is complete.

AppendNote should work. If it is not working for you, can you post a code sample and the error you are getting?

My address is not literally "first.last@company.com". But anyway I received the trace via the thwack message. Here's the error you are hitting: Exception details: System.DirectoryServices.Protocols.DirectoryOperationException: The server cannot handle directory requests. at…

The NCM/NPM database merge happened in NCM 7.3. You still need to call the "AddNodeToNCM" verb in 7.3. The reason for this is that NCM and NPM have independent license counts. Many customers with both products have a smaller license count for NCM than NPM, so you need to specify which nodes you want to manage config for.…

I have a reply to this composed, but I have thus far been unable to post it due to errors with thwack. Let me see if this simple message will post.

Would it be difficult to add the same drop down that is shown on the normal interface screen so that all the charts are updated to that same range? That's probably doable, but it's a bit more than I have time for on the side. You should let Denny or Brandon know you're interested in something like that. Tim

Oh! I see the problem. I don't know why I didn't notice that before. The % character is special in the query string of a Url. It's used for ascii-encoding special characters. ASCII 0x22 is a double quote character. So when your query gets past the REST front end to the query processor, it looks like this: SELECT…

Sorry, I can't help with timelines. But I did add your vote to that case.

Glad to hear you got it working! We don't have a way to clean these up programmatically at this time.

C#

Please start a new thread for this question and provide more detail and context about what you are trying to accomplish.

That's extra strange that it is giving you a weird error and not logging anything. You can use the LogAdjuster tool to get more output. Launch LogAdjuster from the start menu. Find the "Information Service 3.0" component and change the level to "DEBUG". Click Apply. No service restart is needed - it will pick up the change…

StartDiscovery only takes one parameter, so "parameter 0" is the whole thing you are sending. Here's what I missed last time I read your code: you are creating %discoveryProfileXml as a perl hash and then sending that as the PluginConfigurationItem directly. The goofy thing (one of the goofy things...) about this API is…

What response code did you get from the server? Can you share the perl code you used?

Not sure what's going on with your web server. Something seems to be funky with your license keys - the installed software knows it's licensed, but the update is confused. Your options as I see them: (1) call support and get them to beat 9.0 SP2 into submissions or (2) wait for us to finish up 9.1 SP1 which will resolve…

REPLACE is implemented in NPM 12.2 and the other Orion Platform 2017.3 releases (currently in beta).

Orion pings each node every [Node Polling Interval - default 120 seconds]. If no response is received, the node status switches to Warning and we start polling it every 10 seconds. This continues until either we get a response - node status switches back to Up and we resume normal polling - or the "node warning interval"…

This is actually much easier in SQL since we can use the FORMAT function. Like this: SELECT FORMAT(CONVERT(datetime, '16 November 2017 12:26'), 'dd MMMM yyyy hh:mm') Putting it into macro syntax, we would use something like this: ${SQL: SELECT FORMAT(CONVERT(datetime, '${N=Alerting;M=AlertTriggerTime;F=DateTime}'), 'dd…

Good idea! You could also just do the grouping and counting in the SWQL query: SELECT Community, COUNT(1) AS UseCount FROM Orion.Nodes WHERE Community NOT LIKE '' GROUP BY Community

Hmm, that's an old version. If you don't mind me asking, why not upgrade? I don't have a system with 10.6 around to test with, but I looked at the source history to see what functions were available then. I think this query might work: SELECT I.NodeID, I.InterfaceID, I.Node.Caption AS Node, I.Caption AS Interface,…

You did nothing wrong. I looked at the original script that we ship in the SDK package and it has exactly the same problem. I have now corrected this, so the next release will get this right. I'm sorry for the confusion.

I have to ask... are you sure this is the same server?

I don't think metadata publishing is enabled on that endpoint.