IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agentless OS Monitor User's Guides > Agentless Monitoring for Linux User's Guide IBM Tivoli Monitoring, Version 6.3

---

Event mapping

The Tivoli Event Integration Facility (EIF) interface is used to forward situation events to Tivoli Netcool/OMNIbus or Tivoli Enterprise Console.

EIF events specify an event class, and the event data is specified as name-value pairs that identify the name of an event slot and the value for the slot. An event class can have subclasses. IBM Tivoli Monitoring provides the base event class definitions and a set of base slots that are included in all monitoring events. Agents extend the base event classes to define subclasses that include agent-specific slots. For Agentless Monitor for Linux events, the event classes correspond to the agent attribute groups, and the agent-specific slots correspond to the attributes in the attribute group.

The situation editor in the Tivoli Enterprise Portal can be used to perform custom mapping of data to EIF slots instead of using the default mapping described in this topic. For more information about EIF slot customization, see the Tivoli Enterprise Portal User's Guide.

Tivoli Enterprise Console requires that event classes and their slots are defined in BAROC (Basic Recorder of Objects in C) files. Each agent provides a BAROC file that contains event class definitions for the agent and is installed on the Tivoli Enterprise Monitoring Server in the TECLIB directory (install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems) when application support for the agent is installed. The BAROC file for the agent and the base BAROC files provided with Tivoli Monitoring must also be installed onto the Tivoli Enterprise Console. For details, see "Setting up event forwarding to Tivoli Enterprise Console" in the IBM Tivoli Monitoring Installation and Setup Guide.

Each of the event classes is a child of KR4_Base and is defined in the kr4.baroc (version 06.20.10) file. The KR4_Base event class can be used for generic rules processing for any event from the IBM Tivoli Agentless Monitoring for Linux Operating Systems.

For events that are generated by situations in the Disk attribute group, events are sent using the ITM_KR4_DISK event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• index: INTEGER

• index_enum: STRING

• disk_type: STRING

• name: STRING

• block_size: INTEGER

• block_size_enum: STRING

• total_blocks: REAL

• total_blocks_enum: STRING

• used_blocks: REAL

• used_blocks_enum: STRING

• disk_allocation_failures: INTEGER

• disk_allocation_failures_enum: STRING

• free_blocks: REAL

• free_blocks_enum: STRING

• total_disk_space_mb: INTEGER

• total_disk_space_mb_enum: STRING

• used_disk_space_mb: INTEGER

• used_disk_space_mb_enum: STRING

• available_disk_space_mb: INTEGER

• available_disk_space_mb_enum: STRING

• percentage_of_used_disk_space: REAL

• percentage_of_used_disk_space_enum: STRING

• percentage_of_available_disk_space: REAL

• percentage_of_available_disk_space_enum: STRING

For events that are generated by situations in the hrStorageTable attribute group, events are sent using the ITM_KR4_HRSTORAGETABLE event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• index: INTEGER

• index_enum: STRING

• disk_type: STRING

• name: STRING

• block_size: INTEGER

• block_size_enum: STRING

• total_blocks: REAL

• total_blocks_enum: STRING

• used_blocks: REAL

• used_blocks_enum: STRING

• disk_allocation_failures: INTEGER

• disk_allocation_failures_enum: STRING

For events that are generated by situations in the LNX Performance Object Status attribute group, events are sent using the ITM_KR4_LNX_PERFORMANCE_OBJECT_STATUS event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• query_name: STRING

• object_name: STRING

• object_type: INTEGER

• object_type_enum: STRING

• object_status: INTEGER

• object_status_enum: STRING

• error_code: INTEGER

• error_code_enum: STRING

• last_collection_start: STRING

• last_collection_start_enum: STRING

• last_collection_finished: STRING

• last_collection_finished_enum: STRING

• last_collection_duration: REAL

• average_collection_duration: REAL

• average_collection_duration_enum: STRING

• refresh_interval: INTEGER

• number_of_collections: INTEGER

• cache_hits: INTEGER

• cache_misses: INTEGER

• cache_hit_percent: REAL

• intervals_skipped: INTEGER

For events that are generated by situations in the Managed Systems attribute group, events are sent using the ITM_KR4_MANAGED_SYSTEMS event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• subnode_msn: STRING

• subnode_affinity: STRING

• subnode_type: STRING

• subnode_resource_name: STRING

• subnode_version: STRING

For events that are generated by situations in the Memory attribute group, events are sent using the ITM_KR4_MEMORY event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• index: INTEGER

• index_enum: STRING

• memory_type: STRING

• description: STRING

• block_size: INTEGER

• block_size_enum: STRING

• total_memory_blocks: REAL

• total_memory_blocks_enum: STRING

• used_memory_blocks: REAL

• used_memory_blocks_enum: STRING

• memory_allocation_failures: INTEGER

• memory_allocation_failures_enum: STRING

• free_memory_blocks: INTEGER

• free_memory_blocks_enum: STRING

• total_memory_mb: INTEGER

• total_memory_mb_enum: STRING

• used_memory_mb: INTEGER

• used_memory_mb_enum: STRING

• available_memory_mb: INTEGER

• available_memory_mb_enum: STRING

• percentage_of_used_memory: REAL

• percentage_of_used_memory_enum: STRING

• percentage_of_available_memory: REAL

• percentage_of_available_memory_enum: STRING

For events that are generated by situations in the Network attribute group, events are sent using the ITM_KR4_NETWORK event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• index: INTEGER

• index_enum: STRING

• description: STRING

• type: INTEGER

• type_enum: STRING

• mtu: INTEGER

• mtu_enum: STRING

• speed_bps: INTEGER

• speed_bps_enum: STRING

• mac_address: STRING

• administrative_status: INTEGER

• administrative_status_enum: STRING

• operational_status: INTEGER

• operational_status_enum: STRING

• bytes_in_per_sec: INTEGER

• bytes_in_per_sec_enum: STRING

• inbound_discarded_packets: INTEGER

• inbound_discarded_packets_enum: STRING

• inbound_packet_errors: INTEGER

• inbound_packet_errors_enum: STRING

• inbound_protocol_errors: INTEGER

• inbound_protocol_errors_enum: STRING

• bytes_out_per_sec: INTEGER

• bytes_out_per_sec_enum: STRING

• outbound_discarded_packets: INTEGER

• outbound_discarded_packets_enum: STRING

• outbound_packet_errors: INTEGER

• outbound_packet_errors_enum: STRING

For events that are generated by situations in the Performance Object Status attribute group, events are sent using the ITM_KR4_PERFORMANCE_OBJECT_STATUS event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• query_name: STRING

• object_name: STRING

• object_type: INTEGER

• object_type_enum: STRING

• object_status: INTEGER

• object_status_enum: STRING

• error_code: INTEGER

• error_code_enum: STRING

• last_collection_start: STRING

• last_collection_start_enum: STRING

• last_collection_finished: STRING

• last_collection_finished_enum: STRING

• last_collection_duration: REAL

• average_collection_duration: REAL

• average_collection_duration_enum: STRING

• refresh_interval: INTEGER

• number_of_collections: INTEGER

• cache_hits: INTEGER

• cache_misses: INTEGER

• cache_hit_percent: REAL

• intervals_skipped: INTEGER

For events that are generated by situations in the Processes attribute group, events are sent using the ITM_KR4_PROCESSES event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• index: INTEGER

• index_enum: STRING

• command: STRING

• process_path: STRING

• process_parameters: STRING

• process_type: INTEGER

• process_type_enum: STRING

• kr4_status: INTEGER

• kr4_status_enum: STRING

• cumulative_cpu_time: REAL

• cumulative_cpu_time_enum: STRING

• memory_utilization_kb: INTEGER

• memory_utilization_kb_enum: STRING

For events that are generated by situations in the Processor attribute group, events are sent using the ITM_KR4_PROCESSOR event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• user_cpu: INTEGER

• user_cpu_enum: STRING

• system_cpu: INTEGER

• system_cpu_enum: STRING

• idle_cpu: INTEGER

• idle_cpu_enum: STRING

• nice_cpu: INTEGER

• nice_cpu_enum: STRING

• total_cpu: INTEGER

• total_cpu_enum: STRING

• cpu_used_pct: REAL

• cpu_used_pct_enum: STRING

• cpu_idle_pct: REAL

• cpu_idle_pct_enum: STRING

For events that are generated by situations in the System attribute group, events are sent using the ITM_KR4_SYSTEM event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• system_name: STRING

• system_uptime: STRING

• current_user_logins: INTEGER

• current_user_logins_enum: STRING

• maximum_allowed_processes: INTEGER

• maximum_allowed_processes_enum: STRING

• total_running_processes: INTEGER

• total_running_processes_enum: STRING

• allowed_processes_pct: INTEGER

• allowed_processes_pct_enum: STRING

• description: STRING

• system_contact: STRING

• system_location: STRING

• system_date: STRING

For events that are generated by situations in the Thread Pool Status attribute group, events are sent using the ITM_KR4_THREAD_POOL_STATUS event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• thread_pool_size: INTEGER

• thread_pool_size_enum: STRING

• thread_pool_max_size: INTEGER

• thread_pool_max_size_enum: STRING

• thread_pool_active_threads: INTEGER

• thread_pool_active_threads_enum: STRING

• thread_pool_avg_active_threads: REAL

• thread_pool_avg_active_threads_enum: STRING

• thread_pool_min_active_threads: INTEGER

• thread_pool_min_active_threads_enum: STRING

• thread_pool_max_active_threads: INTEGER

• thread_pool_max_active_threads_enum: STRING

• thread_pool_queue_length: INTEGER

• thread_pool_queue_length_enum: STRING

• thread_pool_avg_queue_length: REAL

• thread_pool_avg_queue_length_enum: STRING

• thread_pool_min_queue_length: INTEGER

• thread_pool_min_queue_length_enum: STRING

• thread_pool_max_queue_length: INTEGER

• thread_pool_max_queue_length_enum: STRING

• thread_pool_avg_job_wait: REAL

• thread_pool_avg_job_wait_enum: STRING

• thread_pool_total_jobs: INTEGER

• thread_pool_total_jobs_enum: STRING

For events that are generated by situations in the Total Virtual MB attribute group, events are sent using the ITM_KR4_TOTAL_VIRTUAL_MB event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• total: INTEGER

• total_enum: STRING

For events that are generated by situations in the Used Virtual MB attribute group, events are sent using the ITM_KR4_USED_VIRTUAL_MB event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• total: INTEGER

• total_enum: STRING

For events that are generated by situations in the Virtual Memory attribute group, events are sent using the ITM_KR4_VIRTUAL_MEMORY event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• sum_total_mb: INTEGER

• sum_total_mb_enum: STRING

• sum_used_mb: INTEGER

• sum_used_mb_enum: STRING

• sum_free_mb: INTEGER

• sum_free_mb_enum: STRING

• percentage_of_used_virtual_memory: REAL

• percentage_of_used_virtual_memory_enum: STRING

• percentage_of_available_virtual_memory: REAL

• percentage_of_available_virtual_memory_enum: STRING

---

+

Search Tips   |   Advanced Search