Q1. How do I download the Rules??
Q2. What steps are necessary to install Analysis Rules?
Q3. What steps are necessary to install Statistics?
Q4. What are Error Definitons?
Q5. What interval should be choosen for Statistics or Analysis Rules?
Q6. How are log files monitored?
Q7. What are notification rules?
Q8. What is an Event?
Q1. How do I download the Rules?
Visit the Vault. When you find an Analysis Rule or Statistic Collector you are interested in, right click with your mouse on the hyper link of the name. Select the "Save Target As" and you will be presented with a dialog box for saving to your local machine. Once on your hard drive, you can open you VA2 MMC Console, navigate to the Analysis Rules or Statistic folders, and choose Import.
Q2.What steps are necessary to install Analysis Rules?
To use the Analysis rule several steps must be taken:
1. Download and import the rule as seen in Q1.
2. Edit the Rule if necessary.
3. Create and associate an Error Definition to the Analysis Rule.
4. Create a Notification Rule for the expected Event(s) that could be generated by the Analysis Rule. if one does not exist.
5. Set the Interval to the desired level.
Q3.What steps are necessary to install Statistics?
To install the Statistic navigate to the Statistics folder in the VA2 MMC Console, right click and select the Import option.
1. Edit the Rule if necessary.
2. Set the Interval to the desired option
Q4.What are Error Definitons?
Error Definitions are associated with Analysis Rules. When an Analysis Rule is
triggred, the Error Definiton(s) associated with the Analysis generate an event, which is then examined by defined Analysis Rules. Error Definitions are also used to define Search Strings in log files.
Q5.What interval should be choosen for Statistics or Analysis Rules?
If an Analysis rule is triggered it will send an Event. If Analysis Rules are set to a very high frequency a notification will be generated on each frequency. Generally the bigger the interval the better. For statistics, a data point will be captured with every interval, the smaller the interval the more data will be captured.
Q6.How are log files monitored?
Log files are monitored by creating an Error Definiton and setting the Search String paramater. The Search Screen option supports Perl regular expressions. Then the Error Deffintion is attached to a defined Application or Siebel Component. If defined on the Application level, the Search String will be searched for in all log files defined in the Log File paramater of the Application. If the Error Definition is attached to a Siebel Component, the search string will be examined only in log files for the particular component. When a Search String is found, an Error Event is generated that contains the search string found, and the rest of the values from the Error Definition.
Q7. What are Notification Rules?
Notification Rules examine the Events generated to determine if a particular Event is supposed to cause a notification. A Notification Rule will satisfy the condition and cause a communication to be sent through all defined channels the Notification Rule properties match the Event properties. A Notification Rule can be set to Notify All, in which case it routes all events and effectivly removes the necessity of creating custom Notification Rules. However, when the communications are routed, they will contain the text from the Notification Rule, so a generic "Notify All" rule will not be very helpfull.
Q8. What is an Event?
Events are generated as the result of an Analyis Rule returning false or a Search string defined in an Error Definition being found in a log file. When an Event is created, it is compared against Notification Rules. If a Notification Rule matches the Event, it is Routed to active Schedules. Schedules have Communication Servers associated with them, which have Administrators associated with them, and the defined Administrators(s) recieve the notification.