vinay.by · Manager · ✭✭✭✭✭

Check for permissions provided to the groups in Managed accounts(for folks who cannot mute/unmanage): https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-user-account-access-settings-sw2264.htm On Groups have you selected 'YES' for 'Allow Account to Unmanage Objects & Mute Alerts' ?…

I give up , not sure if its a generic issue or much bigger one, I had the same issue but that was in 2023.4.2 and post creation of new job i hit another error "violation primary key constraint SolarWinds" (there is a workaround for this issue) and i was told its permanently fixed on the latest version. __PRESENT__PRESENT

You can use 'Unmanage schedule utility' for daily maintenance of non-business hours and you can schedule tasks for this to run on daily basis rather than manually doing it https://solarwindscore.my.site.com/SuccessCenter/s/article/Configure-Orion-to-unmanage-items-on-a-scheduled-basis?language=en_US

To get past this - create a new job and run it. Let me know if the new job works or do you see a new error. __PRESENT__PRESENT__PRESENT __PRESENT__PRESENT

Honestly its been a while I worked with ServiceNow and SolarWinds, but then if you are using the standard ServiceNow Integration with SolarWinds in that case I guess it uses "Severity of alert" and there's not much we can do about that and we will need to go with 2 separate alerts. If you are talking about best practices…

If you are passing the severity from 'Severity of the alert' no it cannot be done. You will need to create 2 alerts one for Prod and one for Non-Prod. But if you are forming the severity on the trigger action - custom severity - then yes it is possible using custom attributes on node level. Hope it helps.…

Do you see any Problems, Potential Issues etc in Settings -> My Deployment -> Deployment Health ? If so can you let us know what those are ?

Well done, indeed a good catch.

In that case you can monitor your Primary Poller and Standby Poller through an agent and apply 'Windows Service Monitor' for SolarWinds High Availability Service and customize your email alerts based on Component down alert. The below link should help you with enabling Monitoring.…

I am assuming you are talking about the standard High Availability email alert, Do you have SAM In your environment ? If you do we can easily create custom email alerts based on the services. __PRESENT__PRESENT

Makes sense

This feature is only available in Log Analyzer (paid version), not the SolarWinds Platform Log Viewer. If you have LA then you would see this. __PRESENT

Do you mean to say you want to monitor websites on SolarWinds using SAM for just 2 hours in a day ?

Yes you can, consider the below points as well: 1. I completely agree with @"jm_sysadmin" 2. SolarWinds has not explicitly mentioned anywhere that we cannot have application servers on prem and db on cloud - that being said as best practice what @"jm_sysadmin" has mentioned makes sense - Having Main Poller and Additional…

totally agree, your posts have helped me a lot and I always read them when its from you Thanks a ton

 @"mark.gover" is absolutely correct its not just availability, other factors on the node as well contribute to warning status on the node. And the same will reflect on the group based on what you have selected for the group in advanced tab. DO NOT MAKE CHANGES TO YOUR GROUP UNLESS YOU GET IT APPROVED BY YOUR STAKEHOLDERS,…

You are right in saying that in node summary page it will only list the serial number of the switch that is added trough the IP (which is one of the members) but.. The data is present in Orion, when you add these boxes into your environment do you see a 'Switch Stack tab' into your node details view (when you click on the…

I am guessing the standard global config that you use in your firm is placed on all switches, I wouldn't know what it is but that this should be as part of Standard procedure. Pull up the details/config of the working switch against the one that is not working (this device) - compare the configuration settings - I am sure…

What is it that your pulling out of these reports ? It could be simple or complicated based on your business hours. If you are talking about weekly reports for just 9 hours a day over a week it becomes complicated and you can't use a generic rule. In that case you will need to think about scheduled maintenance on that…

What version are you running on ? Do you access your SolarWinds environment through Additional Web Servers ?

As well after this if its still not connecting do one thing, check to which server is API connecting to is it your primary poller, if yes take a small downtime and reboot your primary poller once. Or reboot the server its trying to access through API. Hope this helps.

Any changes in your environment like upgrade/migrate etc? Or anything that's blocking the port ?

If you look at the SolarWinds requirements it does say you can run 2020.2.6 on 2019 https://documentation.solarwinds.com/en/success_center/npm/content/system_requirements/npm_2020-2-6_system_requirements.htm But then as well NOTE that you are running a 'Unsupported version' (End of Life) and hence if the migration doesn't…

I am assuming you are talking about SAM Component Availability, yes you can build it Add the required fields onto the report like say Application Name, Application Status, Component Name, Component Status etc

@"ImNishat" Lets do one thing, forget the alert for now - keep that as your next point for improvement. You wanted to create a report which provides you a list of devices that fails polling isn't it, please follow the instructions that are mentioned on the below thread - this is what you need at the minute…

I want to alert on: Custom SWQL Alert (Advanced) select that. __PRESENT

Node not responding to SNMP alerts have been a topic of discussion for years and there are several threads on it - you can create a simple custom swql alert Alert on Nodes that stopped responding to SNMP Can we alert for SNMP not responding nodes? Just tweak the query accordingly. Hope this helps.…

Report would be a good thing to have, I would rather say enable the default 'Node not polled in last 10 mins' Alert or create a custom alert for yourself to check if 'Node is not responding to SNMP' this would be more effective rather than looking at it periodically through reports. __PRESENT__PRESENT__PRESENT

Ok makes sense. You did mention 'one that doesn't work is not on a monitored server", have you onboarded your own SolarWinds VM/Server as a managed node in SAM ? If yes create a template on it and place HTTPS URL Monitoring in that template. Even before doing that, login/RDP into your SolarWinds VM/Server and try to open…