HP-UX Event ManagerProgrammer's Guide

viewing and monitoring: the more detail you include in the event name, the more precise the
specification criteria can be. For example, given the event name myco.myprod.env.temp.ok
and myco.myprod.env.temp.high, a system administrator can monitor all temperature-related
events by specifying myco.myprod.env.temp or restrict monitoring to events that report a
high temperature by specifying myco.myprod.env.temp.high.
To avoid confusion and possible incorrect action by the system administrator or monitoring
software, ensure that you provide a unique name to each new event. You can avoid duplicating
a name that is already in use by adhering to the following established conventions:
• For events that are posted by third-party products or applications, ensure the first three
name components identify the vendor of the product, the product, and the program or
product component that posts the event. To ensure that the vendor component is globally
unique, you must avoid choosing two or three initials for this component — instead, use
the full company name or an abbreviation that no other company is likely to choose.
• If you are a user, application developer, or an administrator generally follow the same
conventions that HP recommends for product vendors, identifying the organization in the
first component. However, you can also choose to use the prefix local, because this prefix
must never clash with events that are posted by any externally-developed products that
you may install.
Ensure the second component identifies the application or group that is responsible for
posting the event. For example, your events can begin with the components myco.payroll
or myco.admin.
• The first two components of all events that are posted by a UNIX system are sys.unix,
and the third component identifies the subsystem that posts the event. The use of sys as a
first component is reserved for system events.
To prevent name clashes, do not use the reserved names as the first component of events, except
for its specific naming convention. For more information about reserved event names, see Table 2-2
(page 17). After you have chosen and published an event name, avoid changing it because the
events that an application posts are part of its external interface, and other applications or product
components may depend upon receiving them.
Table 2-2 lists the reserved event names that have specific meanings.
Table 2-2 Reserved Event Names
ExamplesUseName
sys.unix.evm.logger.config_err
Operating system events
sys
local.app.payroll.started
local.app.payroll.started
Local user organization use
local
Available for local test event
posting
test
Reserved Component Names
The more detail you include in an event name, the easier it is for an administrator to use an EVM
filter to find particular types of events. For example, the event sys.unix.hw.registered.cpu
reports that the operating system's hardware management subsystem has detected and registered
a processor. The event contains the hardware ID of the processor in a variable data item and you
can view the hardware ID if you display the event with the evmshow. For more information
about the variable data items, see “Variable Data Items” (page 21). If you are tracing a problem
that is related to that processor, you can use an event filter to select only the events that include
that hardware ID. You cannot filter events by the values of the variables that they contain. You
can only make this selection if the name of the event also includes the information that you want
to select. In this case, the hardware management subsystem makes the selection possible by
EVM Event Content 17