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

defining alerts

Hi,

Can we define the alerts as Critical, Major, and Minor? Do we need to re-configure thru manger or Orion can do it automatically.

2ndly, what's the common practise of the specific threshold for Cisco cpu utilization, server utilization(windows server) and space HDD.

3rd, the points/parameters to be monitored for Cisco router (e.g 3945).

Thanks a lot in advance.

Regards,

sams

Find more posts tagged with

Accepted answers

All comments

Hi sams,

For #1, you can define assign criticality to alerts by adding that in the alert action verbiage. You will need a separate alert for each threshold (for example, >80%.minor, >90% = critical).

For #2, these are typically set according to your requirements. Data sources to determine the proper levels may include the server admins and stake holders as well as the normal utilization as seen in NPM. The decision factors are 1) don't set them too low to where you are getting false positives, 2) don't set them too high to where you won't see an issue. This varies from environment to environment.

For 3# you should be good with the defaults NPM adds (interfaces, CPU, memory etc). You may want to also monitor NetFlow data for examination of who and what are using the bandwidth and IP SLA to ensure quality between routers.

Andy

Quick Links