Comments
-
Although I'm on 11.5.3 and don't have the exact same error in logs - I had a similar issue. Discovery hanging/canceling with errors and upon rediscovery the previous results would append - if I started with 4 nodes it would append 4 more and find 8. The final solution to this was to run a repair for the NPM package on the…
-
Hello roadster, I have the same issue where when exiting with 1 I get the same message. ralfs can you please share what it is you are doing that is letting you avoid that error? And what version of SAM / Orion core you are using? It seems to me like although the script is exiting correctly, it is almost as if solarwinds…
-
I was having an issue with this as well. I can't necessarily tell you how to fix it, however I can give you a workaround that will temporarily fix it. I was getting an issue where it would list https:// using port 443 when solarwinds is only using http. Here's a temp fix: Instead of using "Assign a report", use "Assign a…
-
alth01 - Although I am not using REST api to do discoveries yet (I am hoping to get to that point of automation soon - have been leveraging the API for other tasks) I received nearly the same exact error message you posted above. Discoveries would hang/not complete/or cancel with error. The solution for me was to reinstall…
-
Hello Ganga, Looking at the tables you referenced, this looks like an SQL Query. If you are using the Orion SDK, please try expanding the different entries (I would start with {} ORION) which will give you all the nested tables, then you can look at Orion.Nodes for example. SWQL does not allow the use of * for all fields,…
-
In case anyone wanted the translation to SWQL (better protection from schema changes): SELECT at.Name AS TemplateName , ct.Name AS ComponentName, cd.Name AS ComponentType_, t.ThresholdName, t.ThresholdOperator, t.Warning, t.Critical FROM Orion.APM.ApplicationTemplate AS at INNER JOIN Orion.APM.ComponentTemplate AS ct ON…
-
Ok, I actually started working on a similar problem within my own environment. I made an awesome discovery. Custom properties absolutely are the way to go. The secret to solving this one strangely enough is using alerts. Yes, alerts. First, set up a custom property field to use as a filter as I was mentioning in the above…
-
It would be easier to help you come up with a solution if you could provide an example. I think I understand what the problem is. As far as I can tell, there are no options to define a SQL query within the dynamic query interface, so that is out for an option. I'm thinking your best bet is to define a custom property for…
-
I'm noticing that running the discovery works fine on the Primary poller, but not on additional pollers....
-
Hello bourlis, Nice report! I believe this should resolve your issue: Add the following to the end of your swql statement: GROUP BY A.GroupInfo ,A.MenuName ,OV.ViewTitle ,OV.ViewGroupName ,OV.ViewType ,OV.NOCView Thank you, Justin Valdez Systems Engineer, Tobias International justin.valdez@tobiassystems.com
-
Anything is possible if you believe in yourself. YOU CAN DO IT!!!!!
-
Hello sotherls, Here is one way of doing it - just insert a blank column using : '' as n (you can name this whatever you want, I used n to keep it short), then use point the icon to that column: '/Orion/images/StatusIcons/Small-' + tostring(Nodes.StatusIcon) AS [_IconFor_n] Here is with that added to what you already had:…
-
I believe I may have answered my own question: SELECT EntityName, PropertyName, Name, Value, Type, DisplayName, Description, InstanceType, Uri, InstanceSiteId FROM Metadata.PropertyMetadata WHERE EntityName = 'Orion.Accounts' Will test and see.
