alertprofiles
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revision Both sides next revision | ||
|
alertprofiles [2007/05/11 10:53] faltin |
alertprofiles [2009/01/28 14:40] faltin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | [[TableOfContents]] | + | ====== Alert Profiles ====== |
| - | ====== User manual ====== | ||
| - | A complete user manual for alert profiles is supplied with NAV. Select Help from the sidebar meny and | ||
| - | you will see a link to the pdf. The user manuel goes in detail on the various choices you have in the | ||
| - | user interface (the manuel is not quite up to date at the time of writing). | ||
| - | This document complements tha manual and seeks to give an overall understanding of the NAV alert profile | + | {{tools:alertprofiles.png|}} Alert Profiles was rewritten for NAV 3.5 and now resembles the look and feel found elsewhere in NAV. The functionality is with few exceptions the same as pre-3.5, so the general description given below is still representative. For reference though, you can browse through the |
| - | concept. | + | {{alertprofiles:alert-profiles-manual.pdf|manual of the old Alert Profiles}}. Please keep in mind that the GUI |
| - | + | has changed. We will in due time make an updated manual. | |
| + | |||
| ====== Background ====== | ====== Background ====== | ||
| Line 26: | Line 24: | ||
| alert has any qualified recipients and forwards the alarms. | alert has any qualified recipients and forwards the alarms. | ||
| - | Read more about the EventAndAlertSystem (figure, description of processes, database doc). | + | Read more about [[eventandalertsystem|the event and alert system]] (figure, description of processes, database doc). |
| ===== NAV profiles ===== | ===== NAV profiles ===== | ||
| Line 43: | Line 41: | ||
| improved in terms of user friendliness (we believe). And we have not compromised on | improved in terms of user friendliness (we believe). And we have not compromised on | ||
| flexibility; we have in fact also improved this aspect. | flexibility; we have in fact also improved this aspect. | ||
| + | |||
| + | |||
| + | |||
| ====== How does Alert Profiles work? ====== | ====== How does Alert Profiles work? ====== | ||
| Line 48: | Line 49: | ||
| The Alert Profile concept is explained with an example in the figure: | The Alert Profile concept is explained with an example in the figure: | ||
| - | http://domen.uninett.no/~faltin/nav/alertprofiles/alertprofiles.png | + | {{alertprofiles:alertprofiles.png?800|}} |
| - | |||
| Let us explain this step by step: | Let us explain this step by step: | ||
| Line 67: | Line 67: | ||
| * **In the example:** “At work” has three time periods: mon-fri 8 AM-4PM , mon-fri 4PM-8AM, weekend around the clock. | * **In the example:** “At work” has three time periods: mon-fri 8 AM-4PM , mon-fri 4PM-8AM, weekend around the clock. | ||
| + | |||
| + | |||
| ===== 2) My subscriptions ===== | ===== 2) My subscriptions ===== | ||
| Line 83: | Line 85: | ||
| * **In the example:** On weekdays from 4PM to 8AM my “at work” profile has two subscriptions: | * **In the example:** On weekdays from 4PM to 8AM my “at work” profile has two subscriptions: | ||
| + | * “routers up/down“ => send SMS to 91897xxx | ||
| + | * “critical and emergency alerts” => send email to ''john@univ.no'' | ||
| + | |||
| - | * “routers up/down“ => send SMS to 91897xxx | ||
| - | |||
| - | * “critical and emergency alerts” => send email to ''john@univ.no'' | ||
| ===== 3) Filter groups ===== | ===== 3) Filter groups ===== | ||
| Line 97: | Line 99: | ||
| * Allowed operators are: | * Allowed operators are: | ||
| - | |||
| * Plus/OR (+) | * Plus/OR (+) | ||
| - | |||
| * AND (&) | * AND (&) | ||
| - | |||
| * Subtract (-) | * Subtract (-) | ||
| - | |||
| * Add Inverse | * Add Inverse | ||
| Line 109: | Line 107: | ||
| * **In the example:** I have defined the filter group “routers up/down” as follows: | * **In the example:** I have defined the filter group “routers up/down” as follows: | ||
| - | |||
| * “routers up/down” = “all routers” //AND// “boxstate events” – “trolla-gw” | * “routers up/down” = “all routers” //AND// “boxstate events” – “trolla-gw” | ||
| + | |||
| + | |||
| ===== 4) Filters ===== | ===== 4) Filters ===== | ||
| Line 122: | Line 121: | ||
| * The selection criteria vary depending on the variable in question. The two most important selection criteria are: | * The selection criteria vary depending on the variable in question. The two most important selection criteria are: | ||
| - | + | * equals ( = ) <a single value> | |
| - | * equals (=) <a single value> | + | |
| * IN <a set of values> (in effect an OR operation) | * IN <a set of values> (in effect an OR operation) | ||
| * For string variables various string selection criteria may be used, the most general being: | * For string variables various string selection criteria may be used, the most general being: | ||
| - | |||
| * regexp | * regexp | ||
| * For IP-addresses: | * For IP-addresses: | ||
| - | |||
| * CIDR notation may be used ( IP address / mask) | * CIDR notation may be used ( IP address / mask) | ||
| * **Examples** of two filter definitions: | * **Examples** of two filter definitions: | ||
| - | |||
| * “all routers” : category IN ( GSW | GW ) | * “all routers” : category IN ( GSW | GW ) | ||
| - | |||
| * “boxstate events” : event type = boxState | * “boxstate events” : event type = boxState | ||
| Line 144: | Line 138: | ||
| * Pre defined variables are: | * Pre defined variables are: | ||
| - | |||
| * Event type (or alert type) | * Event type (or alert type) | ||
| - | |||
| * Severity of the alert | * Severity of the alert | ||
| - | |||
| * Category (or sub category) of the equipment related to the event | * Category (or sub category) of the equipment related to the event | ||
| - | |||
| * Sysname or IP address of the equipment related to the event | * Sysname or IP address of the equipment related to the event | ||
| - | |||
| * Relevant room or location information | * Relevant room or location information | ||
| - | |||
| * Equipment type or vendor | * Equipment type or vendor | ||
| - | |||
| * Organization ownership of the equipment in question | * Organization ownership of the equipment in question | ||
| * The set of variables may be expanded by the NAV administrator. In principle any relevant variable in NAVdb may be used! | * The set of variables may be expanded by the NAV administrator. In principle any relevant variable in NAVdb may be used! | ||
| + | |||
| Line 174: | Line 162: | ||
| may be alerts that match the profile, but are not sent due to permission constraints. | may be alerts that match the profile, but are not sent due to permission constraints. | ||
| - | http://domen.uninett.no/~faltin/nav/alertprofiles/ap_permissions.png | + | {{alertprofiles:ap_permissions.png|}} |
alertprofiles.txt · Last modified: 2013/05/08 17:30 by faltin
Page Tools
