Components Of Event Source Hierarchy - Novell SENTINEL RAPID DEPLOYMENT 6.1 - 12-2009 User Manual

Remove selected objects: Removes the selected object along with its children
TIP: Press Shift and click the object to select multiple objects.

9.4 Components of Event Source Hierarchy

ESM displays the information on the Collectors and other components in a hierarchy specific to
ESM.
Figure 9-15
NOTE: ESM allows you to add Collectors, event sources, and Connectors.
Components of the ESM Hierarchy
Table 9-4
Icon Name
Sentinel
Collector Manager
Collector
Connector
Event Source
184 Sentinel 6.1 Rapid Deployment User Guide
ESM Hierarchy
Description
The single Sentinel icon represents the main Sentinel server that
manages all events collected by the Sentinel system.
The Sentinel object is installed automatically through the Sentinel
installer.
Each Collector Manager icon represents another instance of a
Collector Manager process. Multiple Collector Manager processes
can be installed throughout the enterprise. As each Collector
Manager process connects to Sentinel, the objects are created in
ESM automatically.
Collectors instantiate the parsing logic for data from a particular
event source. Each Collector icon in ESM refers to a deployed
Collector script as well as the runtime configuration of a set of
parameters for that Collector.
Connectors are used to provide the protocol-level communication
with an event source, using industry standards like Syslog, JDBC*,
and so forth. Each instance of a Connector icon in ESM represents
the Connector code as well as the runtime configuration of that
code.
An event source server (ESS) is considered part of a Connector,
and is used when the data connection with an event source is
inbound rather than outbound. The ESS represents the daemon or
server that listens for these inbound connections. The ESS caches
the received data, and one or more Connectors connects to the
ESS to retrieve a set of data for processing. The Connector
requests only the data from its configured event source (defined in
the metadata for the event source) and that matches additional
filters.