oithim_yew ✭✭✭✭✭

not that i am aware of. just tweak around else you might need to tweak the alerts for your SQL. for our case, we have issues on the Exchange and since Exchange are memory hogging, we create a custom alerts for these servers.

try to go down little by little. you have to take considerations on the other services using the resources.

I would recommend to do one task at a time, either you upgrade the Orion first with the old DB or migrate the DB to a new SQL server and then upgrade the Orion. For both task, in between, you need to run the Config Wizard.

For this case, you probably need a combinations of a few conditions and there is 'best' strategy. For us, our basic alert would be when the resources reaches our predefined threshold and the time. Example, if the CPU reaches 90% (our warning threshold) and lasted for XX minutes, alerts will trigger. If it is for a few…

Try to explore on the Discovery Central features. But in the end, it was more of an operational and/or process issues to me. Even with this enabled, ones might missed to add this to the monitoring. Automate this (if possible) will create another issues.

First, check what are the 'Status' of the nodes when the alerts are triggered (usually it should be 'Unknown') Second, I would specify the down alert with the "Status==Down' to specifically specify the status of the node Third, I would create another child conditions for that with much more specific conditions. Example:

basically the MSSQL would basically takes up whatever the numbers memory assigned to it unless you controls it. that is how we 'control' it to makes it looks 'good' in the monitoring. i guess this is the way

the rules would applies to all SW. if everything was done but yet, the problem occurs. I guess the best is to try to reinstall SW on the problematic poller. i am not sure about your environment but for us, we have 1 primary and 2 poller sitting at other different countries, if it happens in our environment i might suspect:…

have you tried disabling the syslog or filter some of the things that were coming in instead of processing everything? in our environment, we do not use syslog, hence we discard the message. maybe you can try to filter those that you need and drop those that you do not.

Would it be better to log a case to the SW support but I believe they would refer you to the release notes for the version that you are going to. All the information are there if you care to do some searching, after all sooner or later, you will need to upgrade for the sake of EOL.

There should be a configurations on the MSSQL server which limits the usage of memory on the DB configurations. https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/server-memory-server-configuration-options?view=sql-server-ver17

All, Thanks for the input, I think it should be good to go for me.

yeah but mine are missing. not sure why.

the cart button seems to be missing. I cant remove items from my cart or view the items in my cart

@"jm_sysadmin" Saw your blog and it was great as I am planning for an upgrade next week but I was a bit worried. I had done upgrades before and of all the upgrades, there would be some issues. issues like configurations wizard unable to run or after the upgrade, the services would stop by itself after few days. I was…

got 3 wrong out of 4....a first for me....

hi @"wluther" thanks for the post as I am planning for an upgrade in 2 weeks time. btw, for the primary poller, did you use the offline installer or the online installer (based on the time, seems like it was fast, I believe it was the offline installer) and secondly, for the secondary poller, Solarwinds recommended to use…

Just tested, doesnt work.

Found out that the issue is, the database was 'locked'. Rebooted the SQL and the Orion server, problem resolved.

Found out that the issue is, when the certificate was renewed, the cert was not bind to the default website. We went to the IIS Manager, find the default webpage and bind the certificate to the port 443. Problem solved.

no prob, thanks for the help and below are the version that we are using. I had randomly filter the usage for the whole day and yes, it happens on all the dates that I had choosen from 00:00 till 23:59. i'm having hard time to figure out why the sql server is sending twice the data to poller and we are not sure what it was…

no problem, that is my point. the solarwinds support said that there is nothing much he could do and asked me to reduced the monitoring. well, we are at the minimal level now...anything further will have no point at all. it would be fine if it is a bit higher but we cant justify this to the management if it utilize…

Byrona, Yeah, understand that but it does not make sense for the Solarwinds to utilized more than 1GB of data/day (assuming 300MB/6hrs). And at the same time, how should we monitor the servers across sites/countries if turning a few servers on could slows down the whole network? Might make sense but Martin, Polling…

polling frequency is 300s and case number is 263081. Using WMI for service monitoring. The 300MB for 6 hours is from the monitored server to the Solarwinds server, port 445.

i think i got u, u got it all wrong. the network team are using the manageengine netflow analyzer to check the traffic not the NTA at solarwinds. so am i in the right channel or you put me in the wrong channel?

yes, understand that Solarwinds are for 'network guys' but the management are pushing it to the server team instead.

got it, thanks!

not sure why my post does not come up, u can refer to the 1st questions for the items monitored

i had to 'slim' down the templates due to the high utilizations. the monitoring are even much lesser than the BMC. Component NameComponent TypeEnabledCounterInstanceCategory\Net ServiceWarning ThresholdCritical TresholdCPU Total: Usage (%)Performance Counter MonitorYes% Processor Time_TotalProcessorGreater than 90%Greater…

we're still planning, although the upgrade seems to easy but most of the upgrade that we did, we encounter a lot of weird issues. but since we were assured that we are good to go, i think there should not be any issue in terms of requirements.