klinejw ✭✭✭✭✭

To expand on this...I would like to be able to schedule Transaction A to only run from 8:00 AM - 5:00 PM and then the transaction is unmanaged after hours. Basically we need the ability to apply custom schedules to transactions.

Agree - similarly we have cases where our applications will present an "operator message" that the operator has to acknowledge before they can continue to use the application. This causes the WPM transactions to present false positive down alarms because the original script didn't account for the operator message that…

Excellent! We need to get this released...long awaited features here!

I have wondered this for some time...this product never seemed enterprise ready from day one.

Anyone upgrade a production environment to 11.5 yet? We upgraded last night and we were surprised at how long it took - 6+ hours. We are a fairly large installation with 9 polling engines, 7700 nodes and growing. I think this was a result of background upgrades to tables - Interface errors, interface detail and syslog. Our…

What I was referring to is an automated reoccurring schedule - not a one-time unmanage scenario.

Real-time event log - thank you! Web services - I will be curious to see the implementation of this. This could be huge for us. Auditing - by remediation - are you talking about service restarts, server reboots? If so - Excellent! Keep up the good work and thanks for listening!

I built this using the Custom HTML dashboard resource which contains our own custom web code to perform the searches against the SolarWindsOrion database, so it wouldn't be something I could share on content exchange.

ok...this will work. Any plan to move this capability into the Orion web site so these can be configured there instead of from the Orion server?

We are seeing Business Layer restarts and out of memory messages too...11.5.1. I haven't opened a ticket yet. I attribute ours to polling of domain controllers in UDT. We disabled that today and I was going to see if it keeps happening before I open up a SR.

I would love a special forum for enterprise deployments. We are at 9 APE's, 65K total elements, 30K SAM, 7K nodes. We are adding another additional web site so that we can load balance user traffic better.

Almost all are in the same building, but a good number of them are separated by at least one firewall.

I have it installed in development and while I can't push it as hard as production, I can see some definite improvement. I have about 45 transactions on one player and it appears to be doing very well. We are waiting for the GA release of 2.0.1 before we update production. That will be the real test. We'll keep you…

Solution works.

We are running 2008R2 as well. Our polling engine is managing almost all Windows servers and the majority of our deployed components are Performance Counter Monitor and WMI Monitor types. This polling engine is not short on hardware either - it has 24 cores and 16GB of RAM, but because of the hung processes it averages…

We are NOT going to use the actual primary polling engine for node polling, meaning we are not going to assign nodes to the primary polling engine. All our polling will be assigned to additional polling engines of which we will have 8 of them. Our main concern is when will we hit the wall and have to deploy another primary…

We have the UDT Job status issue as well...no resolution to that case yet. Update: We just received a case update that the UDT Job Status issue is resolved in the UDT 3.2.1 RC1 release which is out in the customer portal. I would prefer this to be a production hotfix versus upgrading the entire module to a RC.

Most of the service level objectives (SLO's) that we deal with at our company are written by business people that don't understand the technology that they are writing the SLA for. If anyone were to ever challenge one of our SLA's legally there wouldn't be anything to contest because of how vague the objectives and…

I think we are going to have to prove that the virtualized database instance isn't going to cut it before we will be able to justify to management that we need to purchase an expensive physical host. I completely agree with you...my years of monitoring experience tell me that we need to go physical on the database instance.

The ability to pass in 'custom' variables into templates would be huge. We have used this functionality in the past to maintain consistent naming conventions as well as populate core monitor parameters.

I'd hold off...Do NOT upgrade to 11.5

Agree...this should have been addressed by now. This along with some other bugs I have reported in the past are preventing this product from going to the next level.

I wrote a query that allow me to filter on that Error Message. BTW - how many nodes do you have on that polling engine? I have 40+ hung CounterFetcher and about the same number of ConHost processes on my polling engine at all times. It seems to take less than 24 hours after a complete restart for them to re-appear. 

1. No, not yet. 2. Yes 3. 7200 nodes, little to no syslog/traps

x2! FTPS primarily for us.

Agree 100%! Go physical on the database! If we grow much more, we are going to have to have our own dedicated host for our SQL instance. Do all active polling from additional polling engines (leave primary to do its job and not worry about polling) - for large installations.

Additional web site or are you running off the primary polling engine? We haven't seen this error, but we are running a dedicated additional web site.

Yes...11.5.2 hotfix 5. This has occurred both before hotfix 5 and after.

Which version are you using? v.2.0 or v.2.0.1 (RC)? I will be interested to see what results you see with 500 transactions in production. In v.2.0 - we start to have problems around 75 transactions per player (at 5min intervals) and those transactions have an average run duration of around 6 seconds. v.2.0.1 seems to have…

Peter...the players that we have tried to run along side our polling engines we left stock. On the standalone players we have tried increasing the thread count with mixed results. In some cases, increasing the threads helped the player scale to more transactions per server and in others it just seems that the player "hits…