Monitoring

Monitoring Rules are defined and activated in Rule Management | Monitoring and they generate events Events are a result of the monitoring component checking your system and collecting information about a specific occurrence that indicates that your environment is displaying uncharacteristic behavior. that are displayed in the Events page.

The Monitor component is set to run out-of-the box, based on default settings. To change the Monitor component settings, see Working with Components. To configure a specific event, see Edit Rule (Monitoring) and to view generated events, see Events.

Monitoring is based on a set of predefined rules that can be configured to suit your environment's requirements (such as performance thresholds) or enabled and disabled as necessary. Once Zend Server for IBM i is installed, the monitor component begins to create events. To find out more about event configuration methodologies, see Working with Monitoring.

From this page you can:

• Run a filter (start typing to filter the display).
• Edit a Rule - Click on a rules name to change the rule configurations.
• See if code tracing for events is active. This means that Events that are set to trigger the creation of Code Tracing information will collect that information when an event is triggered. Additional information about the different code tracing statuses can be found in Monitor.
• See which event actions are set to specific rules. This information is displayed in the main table under the "Event Actions" column.
• Change a Rule's Status - Select multiple rules and apply one of the following changes:
• • Enable Rules - Apply this to disabled rules to start generating events based on the conditions set in the rule.
  • Disable Rules - Apply this to enabled rules to stop generating events.
  • Enable Emailing Action - Reactivate the emailing action. This will trigger an email each time the event is generated.

Note:

Enabling emailing will start to send emails to the system default email address, if you want to send the email to a different address you have to manually edit the rule.

• • Disable Emailing Action - This will disable the emailing action for the selected rules. Once disabled, the rule does not save non-default email addresses and when the Action is enabled the emails will be sent to the system default address.
  • Enable Code Tracing Action - Activates code tracing and a trace file will be generated each time the event is triggered.
  • Disable Code Tracing Action - disables Code tracing.

Note:

To apply changes you must restart the server.

For more information about when to disable a rule, see Working with Monitoring.

In addition to creating issues to display events that occurred, you can define a rule to generate trace information using Zend Code Tracing see Edit Rule to find out how to trigger code trace collection from a Rule.