Skip to main content
Version: 1.12.1

Monitoring and Event Management

The Monitoring and Event Management module enables you to integrate your SimpleOne instance with any preferred active monitoring system (AMS) for supervising the stability and performance of your system. The module automatically reacts to messages received from the monitoring system, while filtering out messages that require no reaction. The event management part of the module records and manages the monitored changes that can be defined as events.

The concept of the module is that as a result of event processing, the system takes certain actions leading to the resolution of problems. The module has tools for flexible configuration and tuning of various rules for responding to events. It reduces the number of spam incidents, and increases the quality of provided services.

Event Types and Processing


Get acquainted with the three types of events (Information, Warning, and Exception). Check the examples to learn how the system handles different types of events.

Monitoring Source


Set up a monitoring system to integrate it with the SimpleOne platform.

Monitoring Rules


Create a monitoring rule to process and structure messages from the monitoring system, as well as to further generate and update monitoring events.

Event Rules and Actions


Configure an event rule to process monitoring events and set one or more actions to be performed by the system when this rule is satisfied.

Demonstration data


You can upload a file with the demodata to your instance to see an example of a configured monitoring system and create examples of monitoring events.

caution

The demodata is only available in Russian.

To deploy the demodata on your instance and create examples of monitoring events, complete the steps below:

  1. Import the SOP-file with the demodata to your instance. Find instruction on how to do that in the Importing Configuration Packs article.
  2. Run the script available at https://your_instance/record/sys_script/165848693511737924. The script will launch the generation of data required for the demonstration monitoring system. It will create incidents, CIs, etc.
  3. Receive the token of the monitoring system user.
  4. Send an API-request to the address https://your_instance/v1/api/itsm_itsm/monitoring_source/v1/monitoring_demo. This request will launch the generation of an example event. You can send the request more than once to add several events. The event records will be added to the Monitoring Event (itsm_monitoring_event) table.
Request body
{
"host": "itglobal.com",
"cpu_usage": "99",
"ram_usage": "99",
"os": "linux",
"error": true,
"subject": "Authentification failed",
"inventory_number": "00016792/2",
"when": "2022-07-22 12:02:43",
"description": "Message Description",
"type": "exceptional"
}
tip

You need the monitoring_message_creator and itsm_event_manager roles to test the module.

The demodata SOP-file contains:

  • 3 records for the Action for Event Rule (itsm_action_event_rule) table
  • 3 records for the Monitoring Event Rule (itsm_event_rule) table
  • 4 records for the Monitoring Rule (itsm_monitoring_rule) table
  • 1 record for the Monitoring Source (itsm_monitoring_source) table
  • 1 record for the API Action (sys_api_action) table
  • 7 records for the Business Rule (sys_business_rule) table
  • 6 records for the Choice Option (sys_choice) table
  • 1 record for the CMDB Class (sys_cmdb_class) table
  • 1 record for the CMDB Model (sys_cmdb_model) table
  • 20 records for the Column (sys_db_column) table
  • 2 records for the Table (sys_db_table) table
  • 1 record for the Import Source (sys_import_source) table
  • 5 records for the Attribute (sys_re_attribute) table
  • 2 records for the Collections (sys_re_collection) table
  • 7 records for the Model Form Element (sys_re_form_element) table
  • 2 records for the Models (sys_re_model) table
  • 2 records for the Model Collection (sys_re_model_collection) table
  • 1 record for the Record Model (sys_re_record_model) table
  • 1 record for the Server Script (sys_script) table
  • 1 record for the Transform Map (sys_transform_map) table
  • 10 records for the Field Map (sys_transform_map_field) table
  • 51 records for the System Translation (sys_translation) table
  • 1 record for the Form View (sys_ui_form) table
  • 2 records for the List View (sys_ui_list) table