klinejw ✭✭✭✭✭

orioncrack - there is a modification to the web.config that will allow pages to be displayed in frames. SW implemented a security fix for cross-site scripting vulnerabilities that broke the frame page behavior.

We have the same issue with MSMQ filling up...so far though in our environment it does not disrupt active polling. We have 8 secondary polling engines. Ticket# 771114

Deltona - so just for clarification, once the 120K limit is reached for a primary polling engine, polling will automatically be throttled or will it only be throttled if polling rates can't keep up with the element load?

I was thinking more along the lines of something like the node search that you can add to the dashboard pages, but this could work for a workaround.

The editing of existing recordings is the single biggest limitation keeping us from puchasing SeUM. If you get that in the product, it will go a long way!

We have hundreds of custom web sites and a pretty good percentage do not have a standard login form with just a username and password. So I am guessing that the HTTP Form Login component isn't extensible enough to accommodate multiple sets of input text boxes to process a login. Our current tool reads the HTML returned by…

I am not looking for a log collector (we already have that and its way overkill for what I am referring to) just a simple log 'browser' from the toolset that my analysts are working from so that if the issue necessitates they can open a 'utility' to view current eventlog entries on the affected server.

We are running the 2.0 beta and while I love the concept of the player load indicator - we are seeing that only a couple invocations of recordings cause that indicator to show 100+ percent. I agree with your logic on the fact that transactions are not created equal. We are going to shuffle around some of our recording…

I think I answered my own question. I have identified firewall drops between the additional web site and the remote polling engine on port 17777.

We have been holding off on upgrades waiting for 11.5.1. We got our major issue with MSMQ backing up resolved (not entirely sure it was related to the upgrade to 11.5) and now our installation is pretty stable. We need to install the UDT (v.3.2.2) upgrade as well to fix the many issues with v.3.2.

Thanks - we'll give it a try.

There are 9098 active SAM components on this polling engine.

If you want to use WMI, don't configure SNMP strings in the discovery config - just configure the windows credentials.

Not sure if this applies 100% to your situation, but we applied a hotfix to our players that replaced the SolarWinds.SEUM.Player.WatiN.dll with a new version to address playback issues. Support indicated that it was a necessary patch for 2.0.1.1060 build of the player. This hotfix wasn't visible on the portal for us, so I…

Why not use the HTTP/HTTPS monitor component or do you need to do something more complex with a script?

Are you talking about creating CI's in ServiceNow from data in Orion or are you talking about creating incidents? Neither here nor there, I have done both with three different ticketing systems now including ServiceNow, HP ServiceManager, and CA Service Desk. All my work has been done outside of Orion with third party…

We are getting a few tickets piling up too... MSMQ backing up due to SWIS - Ticket # 771114 Widgets on views that are slow or fail to load - Ticket # 776355 Exporting SAM templates fails - Ticket # 777974 View UDT Job Status throws UI error - Ticket # 765127 Add...'Manage Transaction Monitors' loads extremely slowly with…

Great information guys...we are in the process of implementing as we speak. When I was talking about 'cores', I was referring to primary polling engines. We are planning on deploying all modules (NPM, SAM, WPM, NCM, VNQM, NTA, UDT). I have successfully pushed a polling engine beyond the 10-12k limit without adverse…

Another good example is that I have opened a "urgent" WPM support case this morning and I haven't been contacted since 9:00 AM central. I would consider this a "system down" situation because our tool is no longer collecting data from two cloud locations. Case # 447066

I think that the various SW modules have different support organizations. We own NPM, SAM, NCM, VNQM, NTA, UDT, and WPM. We get good support so far on everything except SAM and WPM, in my opinion. I know that WPM is a new product and I am willing to give the product a little slack because of that, but I still expect…

11.5.2 has been good for us so far...couple minor things have cropped up, but I can't attribute them to the upgrade. 11.5 was the pain for us.

We have 7500+ nodes using 8 additional polling engines. We do not use primary for active polling. We are running at 64,000 total elements. I don't think you would have any issues with consolidating instances with your numbers. The main concern when consolidating or running a single large instance is your database instance.…

Another item I noticed is that from the additional web site, if you go to Admin -> License Details - under the additional pollers, the poller that is behind the firewall it states it "could not connect to Orion Server on <Polling Engine Name>". It doesn't have this message if you are on the main Orion server web site.

If you setup relationships to nodes or applications, if you remove those it will fix the problem as a workaround...all depending on how many transactions you have in your environment.

Yes - you should be OK. They created a database view with the same name to take place of the old Nodes table. I still one issue post 11.5 upgrade. We have not applied HF4 yet either. 

How many nodes? How many planned elements? I have asked this question many times and it really is dependent on a lot of factors. Without knowing these factors I have some general recommendations: * Make the database instance physical * Optimize the database for extremely high I/O. * When you think it't too big, it probably…

I got this from support at it works for us: Hi Joe, The devs needed time to detail why the change was made - here's what they say: The reason why it's not possible to use it Orions web page for loading into the framework via iframe is not a bug; instead it's a new security protection against Cross Site Request Forgery…

X2! Appears that the API has been updated and the .Net examples are still old and out-of-date.

Yup...x2.

We are running SAM version 5.2. Actually its 5.2 RC3 - but we were told that there was no difference between RC3 and the GA release of 5.2. bwicks - are you running any other Orion pollers on your poller with 11k components? We are running NPM, SAM, and SEUM pollers on the one we are having issues with.