This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
alertprofiles [2009/01/28 14:33] faltin updated for 3.5 |
alertprofiles [2013/05/08 17:29] faltin [Alert Profiles] |
||
---|---|---|---|
Line 7: | Line 7: | ||
{{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 | {{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 | ||
{{alertprofiles:alert-profiles-manual.pdf|manual of the old Alert Profiles}}. Please keep in mind that the GUI | {{alertprofiles:alert-profiles-manual.pdf|manual of the old Alert Profiles}}. Please keep in mind that the GUI | ||
- | has changed. | + | has changed. We will in due time make an updated manual. |
+ | Also see [[http://www.slideshare.net/lunkwill42/nav-alert-profiles|a slideset explaining Alert Profiles]] | ||
====== Background ====== | ====== Background ====== | ||
Line 24: | Line 25: | ||
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 ===== | ||
- | A key design principle for the new alert profile system has been maximum flexibility. We | + | A key design principle for the alert profile system has been maximum flexibility. We |
wanted a system that supports a wide range of user demands. Experience has shown that | wanted a system that supports a wide range of user demands. Experience has shown that | ||
network and systems engineers have an (incredibly) wide range of opinions of how and | network and systems engineers have an (incredibly) wide range of opinions of how and | ||
when they would like to receive alarms. | when they would like to receive alarms. | ||
- | Alert profiles is no doubt a very general and powerful system. The alpha testing of the | + | Alert profiles is no doubt a very general and powerful system. User feedback on the |
- | system has revealed, however, that the downside of being too general is complexity. The | + | system has revealed, however, that the downside of being too general is complexity. |
- | system has been far from intuitive and has required a lot of effort to grasp. A tedious | + | Improvements have been done in the 3.5 version to overcome this. |
- | amount of work has been required for each NAV user to set up his profile. | + | |
- | + | ||
- | As we now are entering the beta phase of NAV v3, Alert Profiles is fundamentally | + | |
- | improved in terms of user friendliness (we believe). And we have not compromised on | + | |
- | flexibility; we have in fact also improved this aspect. | + | |