AutoNOC 2.5 User Guide
Preface
Acknowledgements
System Requirements
Legal

Part 1 - Introduction
1.1 The Ideal Difference
1.2 Automated Operations
1.3 Services & Scaler
1.4 Acquisition Stacks
1.5 Portal Deployment
1.6 Discovery and Crawler
1.7 Monitoring Agents
1.8 Recoiling Database
1.9 Multiple Languages
1.10 Security

Part 2 - NOC Views
2.1 Investigate
2.2 Observe
2.3 Visualize
2.4 Alarms
2.5 Analyze
2.6 Design
2.7 Configure

Part 3 - Model Design
3.1 Object Model
3.2 Devices
3.3 Sets
3.4 Set Criteria
3.5 Probes
3.6 Logs & Events
3.7 Alarms
3.8 Actions
3.9 Reports
3.10 Users
3.11 Polling
3.12 Service Levels
3.13 Dependencies
3.14 Performance

Part 4 - Developer Features
4.1 Adding SNMP MIBs
4.2 Variables
4.3 OSP API
4.4 Probe Template
4.5 Log Template
4.6 Device Template
4.7 Interface Template
4.8 Rebranding

Part 5 - Troubleshooting
5.1 General Issues
5.2 Linux
5.3 Windows

Appendix
A.1 OSP API Functions
A.2 Variables
A.3 Object Reference

3.12 Service Levels
Service levels are at the heart of AutoNOC's ability to evaluate incoming network information and make decisions as to whether the information shows an ideal state or is a condition representing an issue. For more information on these key benefits, please see 1.1 - The Ideal Difference.

The following dialog box shows the service level setting dialog of a probe template:

AutoNOC's service levels work by processing each rule one after another while setting the scope of the interpreter to the relevant database record to be processed. For more information on authoring expressions for the interpreter, see 4.3 - Interpreter. Each expression is evaluated and the first one that is true is the state that is selected for the current element being evaluated.

Service levels represent the current state of the object (when the most recently retrieved data is being analyzed) and they can also represent the state of any data point along the way.

The following are descriptions of each of the columns in a service level definition:

  • Rule Number
    The rule number indicates the number of the rule. You can click on this number in the GUI in order to edit the service level item on that row.
  • Color
    The state color specifies a representative color of the state. Typically green means good, red means bad, and yellow means somewhere in between. The user can, of course, define his/her own choices for these colors. Enter a color in the form RGB (Red, Green, Blue) where red would be "255,0,0", green would be "0,255,0", and blue would be "0,0,255".
  • Text
    State text is a phrase such as "Maxed Out" that defines a user understandable aesthetic literal term that the state of the service level represents.
  • Level
    The service level is an integer between –2,147,483,648 to 2,147,483,647. Typically a value greater than zero means a healthy value. A number less than zero is an unhealthy value. The more positive the value the more healthy and the more negative the less healthy. Service levels can be defined by users to suit any particular needs of their installation.
  • Rule
    The expression is the equation that is solved in order to determine if the current value being looked at is actually in this state. The expression is analyzed as a boolean (true or false) expression. For example, an expression that checks that the relevant value is less than 100 would be "%V<100".

The Rules are evaluated top down and the first criteria that is met is selected as the current state. Be careful when setting up new criteria that you have them in order so that each state can be reached by top down evaluation.

(C) 2007 - All Rights Reserved - AutoNOC LLC
      Call me!