Setting up the ENS Components › Using the Command Line Interface to the Configuration Editor › Add Events

Add Events

See the chapter Understanding ENS for information about events.

To add an event

1. Start the configuration editor:

   $ CONSOLE EDIT /INTERFACE=character_cell
   

2. Enter:

   CM Edit> add event
   

3. Enter the name of the event:

   Event name: Login Warnings
   

4. You are prompted for the class identifier. Enter a name only if you intend to place several similar events in the same category. For example, all events relating to logins could have the class Security:

   Class (DEFAULT:) Security
   

5. You are prompted for the subsystem identifier. This is the part of the serviced system being referred to. For example, if the event refers to Logins, the subsystem could be Logins:

   Subsystem (:) Logins
   

6. Enter a fuller description of the event:

   Information: Login attempt failed
   

7. Enter the text to be scanned for on the console:

   Text: Remote interactive login failure
   

   If you do not enter a metacharacter signifying that the string is a regular expression, the editor assumes your text is a literal string (see the chapter Understanding ENS ).

   If you enter a metacharacter to signify that the string is a regular expression, for example Remote*login failure, then you are asked if you want to match the text exactly:

   Exactly match text? [Y/N] (Y:) Y
   

   Enter Y for a literal string match, or N for a regular expression.

8. Enter information about where the event starts:

   Start [0-999] (0:) 3
   

   For example, a start of 3 means that the event starts 3 lines before the text Login attempt failed.

9. Enter information about how long the event lasts:

   Count [1-1000] (1:) 14
   

   For example, a count of 14 means that the event continues from the start for 14 lines.

10. Enter the priority you wan to assign to the event.

    Priority [1=Critical, 2=Maj, 3=Min, 4=Warn, 5=Clear, 6=Indet] (5:)
    

    4
    

    For example, if it is warning, enter the number 4.

11. The configuration editor asks you to confirm that you wish to enter the event:

    OK to add? [Y/N] (Y:) Y
    

The following is an example of what you see on your screen:

Database contains NO verification errors
CM Edit> add event 
Event name: Login Warnings 
Class (DEFAULT:) Security 
Subsystem (:) Logins 
Information: Login attempt failed 
Text: Remote interactive login failure 
Start [0-999] (0:) 3 
Count [1-1000] (1:) 14 
Priority [1=Critical, 2=Maj, 3=Min, 4=Warn, 5=Clear, 6=Indet] (5:) 4

OK to add? [Y/N] (Y:) Y

Continue to add further events in the same way.