msites ✭✭✭✭✭

LOL no. We are also having to pull SWIS from being used as an API since it goes against security practices. What's concerning is that they are keeping a list of known security holes of their products on a public forum. 

I wish they would include many of the security changes from the KB they have into the customer success report you can self generate in the support portal. We have been battling with support tickets for things like RabbitMQ using known bad ciphers or the product using self-signed certs and the Linux agent repo not being…

Upgraded to 2020.2.1 in September and you guys have left out a very important "Known Issue" item in your release notes that support acknowledges when you call and they state many others have the same issue. If you are using Agents, the poller becomes overwhelmed at startup and will only start working after 1.5-2 hours.…

So does this mean we will have to take security updates more often even though we are not using one of the products? So if we are not using NetFlow and SolarWinds comes out with a critical/high CVE that only is for NetFlow, we would be required to take that update quicker than if we were not using NetFlow since the bits…

Any plans allow 3rd party 2factor auth like Symantec VIP?

Yep, the price increases were wild, but the bigger insult was the amount they increased them with zero new features or better support. Assuming the VC just wants to get their money back as quickly as possible before they sell the company off again. 

That's my favorite reply from the support team of a software company that sells critical monitoring software. "Just ignore the alert from the alerting platform"

I use custom properties that owners set on their nodes and then we alert based on that value. Below is a basic example. Our base windows image is 120GB C drive, so that's why we have this specific alert, but we have many different custom properties values the users can pick from. 

Is there a specific time that the alerting stops working, or is it at random? When this occurs, is everything still polling just fine? 

Someone pointed out in another post that the release notes were once again published without having all of the "Fixed" issues there, which in my mind also means there are missing "known issues". 

That's very concerning that such a major issue was "left out" from the release notes. What other items were left out and what other Known Issues were not put on the release notes that we should be aware of prior to the upgrade? 

There hasn't been a stable release in over a year...i'll let you go first 

If I could go back in time, I would have stuck with 2020.2.6 or whatever the latest is BEFORE they started to merge the products and created this mess. 

I HIGHLY recommend opening up a support case and having Tier 2 (not Tier 1) review the logs to make sure you do not have an underlying issue. We had the SAM Maintenance overdue message for a long time, but when we upgraded to 2022.4 we discovered that our OrionLog database wasn't keeping it's normal size. There was another…

We have the same policy of being forced to take upgrades when they have CVEs listed and which means we are always early adopters of the super buggy upgrades with little help. If we could go back in time, we would take that 2020.4 release and stick with it as there have been zero real new features released in 1.5 years,…

yes, I wouldn't touch 2023.x for a long time. Once they started to merge things with 2022.3+ it's been 17 bugs after 17 bugs with each release. 

Thanks for this! This just started for us on Sunday and it's getting bad. What's super frustrating is that I spent half my day proving to Tier 1 that it wasn't a SQL database issue. Then I finally get to Tier 2 and they are like "yea, it's a known issue" within 5 minutes of the call. It's also crazy that when they have…

How about a hotfix as it's causing outages of critical monitoring infrastructures...

A few weeks ago I received an alert that a drive on our Orion database server was growing. After further investigation it looks like the SolarWindsOrionLog seemed to be growing about a gig a day. After looking at the tables I noticed data that was well over the normal 7 day retention we have for those types of events.…

was told it's not scheduled to be fixed until Q3 2023.3 or later. 

Do you mean like a webcheck and searching for test on that page? You can add the HTTP/S monitor component to the template.

Same, we want the security fixes, but not the bugs in 2023.1 where a non-admin user using perfstack can cause a system issue. 

support said it isn't slated to be fixed until 2023.3...so only a few more months! 

Yes. We and others have been entering security requests for this as a self-signed cert is not allowed in our enviroment based on security standards. They finally introduced it (although we haven't taken this update based on the current known issues). 

We requested the same thing a few years ago and were told the API calls can only go to the MPE. With 2023.1 they are also allowing us to change the API port over to a new port that will allow you to use a real cert that isn't self-signed. 

Are you deploying agents or adding nodes manually via the WebUI? We use SCCM and ansible for deployments and have different configs for areas to help semi load balance our pollers. It's not perfect and we still move nodes manually from time to time, but it helps by not having all new nodes going to the same poller. When we…

We put in a feature request for this a while back after we converted to SAML/SSO as we don't want to have a admin account that people can use to login with. Such weird security holes and poor design. 

Mass deploy an agent on Windows (solarwinds.com)

That would be too secure lol You can install with a mst file which doesn't require a username or password. That's how we currently do it as we don't use local users or ad linked users (SAML/SSO type do not work for agent installs)

Just went down a rabbit hole. I'm 99% sure this is making a call from the end-user side based on following the path.