Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

User Access Limitation

I have a question. Is there a limitation on users access to Orion? I'd like to give Users (dept wide) access to our Orion Summary Page to access our Reports. Is there a limitation or what limitations do you forsee when say 500 users access this site at once pulling and looking at Reports.

I have a Windows 2008 64bit server with 12gb RAM, 16 CPU's that house my Application, WebServer components and I am running NPM and heavy APM usage as well.

1. Is there a way I hide Reports. I like your out of box reports but I dont want it available to everyone.

Thanks,

Find more posts tagged with

Accepted answers

All comments

borgan

Regarding access to reports - yes you can limit access to reports in a few ways. Probably the best way is to place the Custom List of Reports resource directly on the Orion Summary Page. You will then pick only the reports you want them to access in that list. You could then remove the Reports link from any menu bar so the user could not access any other reports.

If you really did have near 500 users logged on to that server at one time, you could well see a big hit on the resources. Adding another web server could help with that. What is the current polling rate listed on the Polling Engines page?

Jay_Cummings

In your scenerio of 500 users hitting the Orion home page at the same time - and then possibly pulling reports - you will see things like:

IIS will be over burdened and your web access for all users will suffer
your database will be hit very hard (you didn't mention details about your SQL location and specs)
polling, alerting, and other general functions may experience unacceptable problems (missing polls, data unavailable, slowness, etc.

BOrgan has given great advice for options to limit user access to reports (assuming you want them to have any access at all). You also have the option of removing report access completely for users by choosing No Reports or a sub-set of reports that you maintain in a sub-directory under Reports.

Other things that can be done to actually enable 500 simultaneous web users include:

Additional Web Server(s) with enough horse-power for IIS to present the pages in a timely manner. This will spare your primary polling engine and ensure that the impacts aren't effecting polling, alering, etc.
Additional polling server may help if the current load is heavy on the single polling engine (understanding the polling rate question asked by BOrgan is fundamental to knowing which of these options will benefit you)
Create a streamlined home page and limit users to only seeing that page (keeps the amount of data pulled down to what's necessary)
Limit casual users to only one tab & one page (limits data hits for surfing Orion)
Limit users to specific sets of nodes/groups (again lessining the data needs)

If you need more feedback, just let us know.

Key statistic items include: hardware specs (Orion & SQL & other polling engines), modules in play, number of monitered items (elements, interfaces, volumes, nodes, applications, NTA sources, traps, events, syslog, etc.), polling rate, CPU/RAM/disk trends for Orion & SQL (if you aren't already monitoring the Orion & SQL servers, start now), etc.