OMNIBUS EIF 7.3：事件集成设施参考指南

需积分: 9 22 浏览量更新于2024-07-22 收藏 524KB PDF 举报

本资源是关于IBM Tivoli Netcool/OMNIbus Event Integration Facility (EIF) 的参考手册，版本为7 Release 3，产品编号为5724-S44。适用于所有后续的发布和修改，直到有新的版本说明。该手册由国际商业机器公司（International Business Machines Corporation）于2003年和2009年版权，特别指出在使用前应阅读第73页的“注意事项”。该手册的主要目的是向目标读者提供关于OMNIbus EIF的全面了解，包括其概述、适用受众、内容结构以及与Tivoli技术培训和支持信息的关联。手册旨在帮助用户理解和操作OMNIbus，一个关键的事件整合工具，它在企业级IT监控和管理中扮演着重要角色。 "About this publication" 部分会介绍手册的背景和目的，可能涉及编写目标、目标读者的技能要求以及手册如何配合Tivoli整体解决方案使用。此外，可能会提到手册的发布历史和更新信息。 "Intended audience" 部分详细说明了谁是本手册的主要读者，可能是IT专业人士、系统管理员、网络监控工程师或对OMNIbus有需求的IT管理人员。这部分可能还强调了针对不同角色的阅读建议和可能遇到的特定关注点。 "What this publication contains" 部分列出了手册的具体内容结构，可能包括但不限于：OMNIbus EIF的架构和工作原理、配置和安装指南、API和接口文档、示例和案例研究、故障排除和问题解决策略，以及性能优化和最佳实践。 "Publications" 部分可能会列出相关的参考资料，如其他Tivoli Netcool系列文档、技术文档、白皮书或在线资源，以供读者扩展学习。 "Accessibility" 和 "Tivoli technical training" 部分会讨论如何获取和利用官方的无障碍支持，以及通过哪些途径可以获取到Tivoli提供的针对OMNIbus EIF的专业技术培训。 "Support information" 部分会包含IBM针对OMNIbus EIF的官方支持政策，如技术支持热线、技术支持网站、常见问题解答、更新通知等。 "Conventions used in this publication" 部分则介绍了手册中使用的术语、符号、颜色编码和排版风格，以确保读者能够顺利理解和解读内容。本手册是Tivoli Netcool/OMNIbus Event Integration Facility的重要参考资料，涵盖了从基本概念到高级操作的全面指导，对于有效管理和优化企业IT环境具有重要意义。

event, while other sources are brief in their descriptions. An adapter converts all

events into a format that provides consistency in information, such as the source,

location, date, and time of an event.

Some events, such as traps, contain data that you cannot read. In these cases, the

adapter must translate the data into a format that you can read so that the

information can be further processed. Some sources, such as a system log file,

provide data that you can read without machine translation.

Adapters translate event information into a set of attributes. Each attribute is

predefined by the adapter and contains the attribute name and the attribute value.

The adapter places the appropriate information in each attribute, and then sends

the event to the event server.

This following figure illustrates how an event evolves:

The following example shows how log file information is translated into events. In

this example, a failed attempt to run the su root command on the host oak is

written to the system log file. You can read the resulting format:

Nov 7 08:51:42 oak su: 'su root' failed for don on /dev/ttyp0

The adapter then translates the log file information into an event as follows:

Su_Failure:

source=LOGFILE;

origin=oak;

date=”Nov 7 08:51:42 ”;

host=oak;

sub_source=login;

from_user=don;

tty=/dev/ttyp0

to_user=root;

END

Related concepts

“Event server” on page 5

Adapters

Adapters are processes that monitor managed sources. A source is an application

such as a database, or a system resource such as disk space. When an adapter

receives information from its source, the adapter formats the information and

forwards it to the event server.

To monitor a source such as a third-party or custom application, you must use the

Event Integration Facility to create an adapter and event classes for each new

source.

Adapters monitor sources in the following ways:

event:

native format

event:

Tivoli format

To event server

System

Resource or

Application

Event

Adapter

Figure 1. Evolution of an event

Chapter 1. Overview of the Tivoli Event Integration Facility 3

v An adapter can receive messages from a source that actively produces messages.

For example, adapters can receive messages that are sent by Tivoli software

applications.

v An adapter can check a file at configurable intervals if the source updates a file.

v An adapter can poll a system resource or system condition at configurable

intervals, and then interpret and forward the resulting information directly to

the event server.

Event classes

Event classes are classifications of events. After separating information into event

classes, adaptors format the information into messages that represent specific

instances of event classes. Then they send the information to the event server,

which processes the information, along with information received from other

adapters.

Event classes can be divided into subclasses to facilitate a further breakdown of

information so that more detailed rules can be applied to the event information.

Essentially, event classes are an agreement between the adapter and the event

server about what information the adapter sends to the event server.

Note: Event classes are not the same as Tivoli objects.

Related concepts

“Defining event classes” on page 26

Configuration files

You can control the behavior of an adapter using the configuration file. A

configuration file enables you to specify configuration parameters.

You can specify the following configuration parameters:

v The information that must be sent to the event server.

v The connection interface used by the adapter.

v The host on which the event server is located.

v The event filtering to be performed by the adapter.

v Any information that is unique to a particular adapter.

After information is separated into event classes, the adapter sends the information

to the event server for further processing. You can use the configuration file to

control the information that the adapter sends to the event server in order to

reduce the load on the network.

You do not need to modify multiple instances of an adapter to run in different

environments. You have to modify only the configuration files.

Related reference

Appendix D, “Keywords,” on page 63

4 IBM Tivoli Netcool/OMNIbus: Event Integration Facility Reference

剩余91页未读，继续阅读

qq_25827321

粉丝: 0
资源: 1

OMNIBUS EIF 7.3：事件集成设施参考指南

Omnibus

omnibus中文用户手册

registry.gitlab.cn/omnibus/gitlab-jh和gitlab/gitlab-ce的区别

gitlab windos安装

多重共线性检验python代码

win部署gitlab

最新资源