This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Schedule Orion Discovery through API

Hello all!

I am trying to setup a lambda function to automatically add nodes to Solarwinds and discover volumes and devices using the discovery tool. Now I can do this with SNMPv2 no problem, but I run into an issue with WMI for our Windows nodes as when they're created they are not yet on the domain and can't authenticate correctly using the discovery tool.

Is there a way through the API to schedule a discovery to take place so as to delay the process to allow our node to build, join the domain, and reboot? 

I am currently using this for all of the nodes that get added

swis.invoke('Orion.Discovery''StartDiscovery'discoveryProfile)
I was wondeering if there's a way to instead of 'StartDiscovery' do a 'ScheduleDiscovery' after half an hour or an hour.
Thanks!
Parents
  • The only thing I could find is a property "CronSchedule" under Orion.DiscoveryProfiles but when I tried to do a Set-SwisObject on it I get Operation not supported on Orion.DiscoveryProfiles.  I may have done it wrong

    Set-SwisObject $swis "swis://xxxxxxxxxxxxxxxxxx/Orion/Orion.DiscoveryProfiles/ProfileID=95" @{"CronSchedule"='<?xml version="1.0"?><ReportSchedule xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:xsd="">www.w3.org/.../XMLSchema" xsi:nil="true" />'}

    The code above was me trying to set a discovery to manual. Sorry I did not have any luck but maybe this may spark an idea with someone. 

  • I had looked into this as well with little success. When I pull a manually created discovery from GUi I get

     for CronScheduler

    '<?xml version="1.0"?>\r\n<ReportSchedule xmlns:xsi="">www.w3.org/.../XMLSchema">\r\n  <FrequencyId>0</FrequencyId>\r\n  <StartTime>2021-05-17T14:10:00Z</StartTime>\r\n  <EndTime xsi:nil="true" />\r\n  <DisplayName>Schedule</DisplayName>\r\n  <CronExpressionTimeZoneInfoId>Eastern Standard Time</CronExpressionTimeZoneInfoId>\r\n</ReportSchedule>',
    Though I don't know how to go about extrapolating that into a useful query. I tried to modify the time and see if it took the change but it just starts the discovery right away.
  • I do not think you can modify the schedule from the api or orionsdk.  Well I have not found a way and it looks like 80+ people have viewed this thread that did not have a way. 

    I think there is a way to add a node and just let the normal pulling cycle finish but not sure if you can define what is monitored.

Reply
  • I do not think you can modify the schedule from the api or orionsdk.  Well I have not found a way and it looks like 80+ people have viewed this thread that did not have a way. 

    I think there is a way to add a node and just let the normal pulling cycle finish but not sure if you can define what is monitored.

Children
  • I'll dig into this a little, maybe, but we might just go with a nightly discovery on our subnets. I know that'd tried adding the node and letting it see if it polls on it's own and picks it up, but it does not. At least not statistics like volume, interface, and maybe ram usage.