tony.johnson ✭✭✭✭✭

And so my last note got me thinking, it's not ideal to unmanage/remanage the node after deleting the volume. Thankfully volumes have unmanage/remange capabilities too. Adding the unmanage action against the volume prior to deleting is a better approach and works well in my testing.

This looks to be a discrepancy between the actions for deleting a volume in the UI and the generic entity deletion actions exposed via the API. I have opened CORE-17992 to track this. Right now I do not see any immediate workaround. Deleting the offending entry from the NodeChildStatus table directly does not update the…

Hi @"alankar.srivastava" I am looking into your case now. 

@"mcrummett" Your very welcome, this has spurred me into working a little bit more with python and honestly I think I may be hooked :-) Check out this post when you have some time. https://thwack.solarwinds.com/product-forums/the-orion-platform/f/orion-sdk/90898/python-api---credential-manager

I would highly recommend the following blog post which covers these topics thwack.solarwinds.com/.../intro-to-api-sdk-swql

swis.bulkupdate can be passed a list of Uris and it will update them all, whereas in this case we are only updating a single Uri and so swis.update is more suitable as it accepts a Uri as a string type

Here is what I have come up with as starting point. It needs more commenting, code cleanup, better error handling, and some polish but should be enough to get started. The script provides 3 options 1. Create a new SNMPv3 Credential. 2. Update an existing SNMPv3 Credential. 3. Assign an existing SNMPv3 Credential to a list…

There is not method to do this via the API that I am aware of.

There is no equivalent widget type available in Modern Dashboards, the closest available for now is the Table Widget. You likely already have the query but I would start with something like this SELECT Apps.Application.StatusDescription, Apps.Application.Name as ApplicationName, Apps.Application.Node.Caption as Node FROM…

I see 2 options here 1. Update an existing SNMPv3 credential set. This will apply to all nodes which have that credential assigned. 2. Create a new SNMPv3 credential set and assign it to a list of specific nodes based upon I.P Address. it sounds like you may need both options?

I see the problem now. What version of the Orion Platform are you running? I believe this has been addressed and is not reproducible in my 2020.2.5 Lab. KPI widgets should resize without the addition of a scroll bar The Color Palette for the default color has also been updated

That example allows you to change the credential assigned to a node from a list of existing credentials. The credentials are seen in the Orion.Credentials entity SELECT Name, Description, CredentialType, CredentialOwner FROM Orion.Credential Do you want to create a new SNMPv3 credential definition and then assign it to a…

Ok that was not soo bad after all, here is what worked for me import requests from orionsdk import SwisClient npm_server = '' username = '' password = '' verify = False if not verify: from requests.packages.urllib3.exceptions import InsecureRequestWarning requests.packages.urllib3.disable_warnings(InsecureRequestWarning)…

Ahh Python... I really must learn it someday. For now, all I can offer is a possible solution in this example below until I use this as an incentive to finally set up python to run on my windows machine. https://github.com/solarwinds/orionsdk-python/blob/master/samples/bulk_update.py

I am sorry to hear that, could you share the case number with me? I would like to run his down to see where we can improve.

Thank you for the update. Did you identify this through trial and error or did you open a support case?

linked updated now thank you.

When muting alerts with a schedule, the entries remain in the Orion.AlertSuppression after the SupressUntill date has passed. Clicking Resume Alerts (Unmute) on a node, with or without an end date, will clear the entry. The option to unmute is not possible after the end date. For now, it seems this behaviour is consistent…

Not all credentials in Orion.Credential can be updated using the API. What credentials are you trying to update?

Hello, Apologies for the tardy response. Have you overcome the problem now?

Honestly, I am not certain what the expected behaviour is for the Orion.AlertSuppression entity but will run this down to find out. Are you seeing any unexpected behaviour with the muting of alerts that leads to this question?

Hi viyayni, Can you describe this in a little more detail to help me understand what you would like to achieve? At the moment widgets can be resized across 12 columns and vertically sized as needed. 

For existing nodes and existing credentials, there is an example discussed here link

Within the user links resource when places on a node details view it is possible to use any node variables such as thise listed here https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-node-variables-sw3485.htm . You may also use custom properties in the same format to construct the url you…

I do not have a query such as this readily at hand, are the VMs of interest being monitored as nodes in Orion?

Yes, that is correct. You could define the profile through the UI including the schedule and then extract for example the CronSchedule field and use this value to update the field in another profile.

It is not possible to create/update a discovery schedule using the API. It is possible to update the DiscoveryProfiles table directly in the database. There are 2 types of scheduled discovery. * The Basic schedule, Hourly or Daily. These get a default value in the CronSchedule Field. <?xml version="1.0"?> <ReportSchedule…

Here is an example I use to update Nodesettings to change assigned credentials. Update Nodesettings to change assigned credential. # Connect to SWIS Import-Module SwisPowerShell Add-PSSnapin SwisSnapin $hostname = "127.0.01" $swis = Connect-Swis -Hostname $hostname…

This is likely the offline installer and an offline machine. The problem is that the Windows machine is not up to date and has no knowledge about the updated certificate. The error is described in more detail here support.solarwinds.com/.../Authenticode-verification-UnknownError-after-upgrade-to-Orion-Platform-2020-2-4 The…

Your initial query was looking for all dates for a particular month i.e give me ALL the Januarys you have. The change takes uses the dates as a range and asks for everything less than the current month and greater than the last month.