UNABLE TO FIND IMPORTED NODES AFTER DISCOVERED

Have you tried searching by IP address in the search nodes widget of the summery screen?  Everything below here is assuming that the nodes were created, you just cannot find them.  If they are just not getting created, then that's a different issue.

If you find it named something strange, usually the node is named by the reverse DNS entry for the IP address.

If you have SWQL studio, here is a query to see the latest nodes created.  If you don't have it, then you really should go download the orionSDK at: github.com/.../releases

select top 100 Caption, IPAddress, Created from (
    SELECT
        n. Caption,
        n.IPAddress,
        (SELECT top 1 ToLocal(ae.ObservationTimestamp) as CreatedDate FROM Orion.AuditingEvents ae Where ae.netobjecttype='N' and ae.netobjectid=N.NodeID and ae.ActionTypeID=25) as Created
    FROM Orion.Nodes N
    where (SELECT top 1 ae.ObservationTimestamp as CreatedDate FROM Orion.AuditingEvents ae Where ae.netobjecttype='N' and ae.netobjectid=N.NodeID and ae.ActionTypeID=25) > AddMonth( -1, GetDate() )
) p
Order by Created desc

If you don't have SWQL studio, then I guess you can run the query here: https://<your solarwinds server>/Orion/Admin/swis.aspx

but really.. download the SDK and use SWQL studio.

Hello Brscott, 

I will try this.

For sure I had tried searching the IP Addresses on the search widget and could not find them.

Thank you for the response.

you 'could' also run the query in:

https://servername/Orion/Admin/swis.aspx

change "servername" for your server

I'm not sure my discovery is working either.  I am still looking at it.  Seems I have badgered my users enough that they are creating the nodes before discovery can find them, so I don't have any good examples.  I am seeing strange things, such as discovery shows that it discovered a node on 11/15/24, but I show that it was already created on 10/30/24... that and some other things just not adding up.

I had a similar issue with this a few months ago, it was due to account limitations. We had accounts with limited access to certain nodes via custom properties in the account setup. Verify they listed with an account with full admin access.