dan_jagnow · Senior Architect

Comments

  • Network Atlas maps cannot be updated via an API. Future releases of Orion Maps (Orion Platform 2019.2 - Orion Maps 2.0! ) may support API-based manipulation.
  • This performance problem is now being tracked with internal issue number NPM-13219.
  • If I understand what you're trying to accomplish, I believe you should change 'DisableIcmp': False to 'DisableIcmp': True in your Discovery profile settings.
  • You might also want to check the Orion.InformationService.log file on your Orion Server. Run your script to cause the error, then open this file: C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log Locate the exception near the end of the file, and post it here.
  • I put together a PowerShell script to try to reproduce your issue. I tried to initialize $targetNodeProps with values that were as close as possible to the output you shared. This runs without error for me. If you hard-code the values in the creation of $targetNodeProps, do you still encounter the error? Obviously, you'll…
  • If you haven't yet, you should read the Orion Platform Migration Guide. There are several possible approaches. If you can, you might want to consider using the same IP address and hostname to minimize the migration effort. If you aren't able to do that, though, the guide does explain how to redeploy or reconnect agents.…
  • Happily, you don't have to provide the full XML. You can just update the Enabled property like the script below. This example is for updating a single action, but you could adapt it to handle multiple actions for a bulk update. Import-Module SwisPowerShell # Connect to SWIS. $hostname = "myserver" $username = "muser"…
  • This appears to be a bug in the product. I have contacted the IPAM team, and they are investigating.
  • SWQL supports functions like GetDate and MinuteDiff that should allow you to build an appropriate WHERE clause. For reference, see SWQL Functions · solarwinds/OrionSDK Wiki · GitHub
  • If you have Web Companion by Lavasoft installed (possibly from installing FileZilla), then this support article may apply to your situation: Website will not load: Orion module engine unable to talk to swis v2 after installing Web Companion by Lavasoft - SolarW… There is also some useful information about testing…
  • Looking at the error message, it seems like you are connecting to SWIS without any problems. You've probably constructed your curl request correctly. SWIS is trying to invoke the ConfigSearch verb, and to do that it's trying to open a Windows Communication Foundation (WCF) connection to the NCM business layer, which is…
  • I would expect that you should be able to copy your query without issues. Can you supply the full text of the query that you're trying to execute? The screenshot is useful, but it only gives so much detail.
  • If you open it up in SWQL Studio you'll get a preview that suggests the form of XML it's expecting: If you copy the XML in deviceTemplate and tidy it up, you'll have something like this: <?xml version="1.0"?> <DeviceTemplate xmlns:i="">www.w3.org/.../XMLSchema-instance"…
  • I assume you want a single row per node in your final report? I'm not sure if that is possible with SWQL. Here's an example of how you could retrieve information about the interfaces for each node in SWQL, but this will return one row per node/interface combination: SELECT TOP 100 n.NodeID, n.DisplayName, n.IPAddress,…
  • Additional details about your script would help. Be sure to read through the Orion.AlertConfigurations section in the Alerts documentation here: https://github.com/solarwinds/OrionSDK/wiki/Alerts Because the desired behavior of the alerts is captured in XML, you could invoke the SWIS Export verb on…
  • This is untested, but something like this might work. It will likely be slow, though: SELECT oa.OperationInstanceID, oa.RecordTime, oa.OperationStatusID FROM Orion.IpSla.OperationAvailability oa WHERE oa.OperationStatusID <> ( SELECT TOP 1 oap.OperationStatusID FROM Orion.IpSla.OperationAvailability oap WHERE…
  • The notes associated with nodes are stored in Orion.NodeNotes. See Orion.NodeNotes | Orion SDK Schemas for details. For an example of how to create node notes, see the comment from tdanner​ on this issue: https://github.com/solarwinds/OrionSDK/issues/55
  • I haven't found any step by step instructions for this particular integration, but there is general information about integrating SolarWinds Orion with third-party ticketing systems here: https://support.solarwinds.com/SuccessCenter/s/article/Third-party-ticketing-system-integration
  • I don't believe that you can currently manage the application components via the API. See this thread for details: Orion.APM.Component - Delete or Create individual components using API Feel free to submit a feature request for this!
  • I don't have IPAM installed right now to test this, but I believe you may need to use IPAM.AttrDefine. SolarWinds Information Service v3.0 Schema Documentation You'll find some discussion of custom properties for IPAM in the IPAM wiki documentation (search for "custom"): IPAM API · solarwinds/OrionSDK Wiki · GitHub