Infrastructure Settings for Applications

• Allow automatic deletion of direct assignments

• Create suspended deployment jobs

  Set to true to create deployment jobs with the state suspended, instead of pending. Note that this does not affect deployment jobs created when synchronizing installed packages or policy template assignments.

• Enable automatic assignment
• Send event when assignment is created
• Time interval to scan for changed topology
• Update existing assignments

Default Agent Heartbeat Interval Interval (in minutes) at which the agent sends heartbeat events to the server. The heartbeat interval begins when the agent processes are started. You can change the default for each monitored node or connected server in the properties.

• Default Grace Period
• Default Health Check Type
• Enable Health Check
• Enable Health Checks on New Agents
• Log Only OK Events
• Maximum Number of Parallel Server Checks
• Severity of Agent Health Problem Events

• Number of concurrent deployment jobs for package deployment
• Number of parallel running threads for template and setting deployments

• Number of retries of failed jobs
• Wait period until a failed job is restarted

• ArcSight Logger server selection script
• SiteScope server selection script

• Disable template syntax check

• Allow command execution through Action Web Service

• Audit Category
• Enable Auditing

• DDM Domain Name
• Dynamic Node Generation Enabled
• IP Ranges
• Node Name Patterns

• Cache Modification Configuration
• Cache Refresh Rate
• Cache Type
• CI Limit
• CI Limit Event Fully Qualified Domain Name
• CI Resolver Attribute Splitting Rules
• CiInfo Host Separation Character
• CiInfo Key Separation Character
• Database Cache File Path
• Fast Result Cache
• Ignore duplicate CI cache entries
• Limit CiInfo Results Per Keyword
• Query Chunk Size
• Resolution Retry Time

• Resolve Impacted CIs

  Set to true to display impacted business applications and services as custom attributes in the Event Browser.

• TQL Queries
• Use Topology Sync Shortcut

• Certificate Server IP Address

A new event can be used to automatically change the lifecycle state of one or more existing, related events. When a new event is received, a search for existing, related events is made. If any related events are found, these are closed or set to resolved and replaced by the new event.

There are two ways in which events can be related:

• closeKeyPattern attribute

  If an event comes in and its closeKeyPattern matches the key attribute of an existing event, the older event is closed.

• ETIs Contributing to Health

  Events can be related when they all contain an ETI contributing to health. The value of the ETI of the new event must be different from the value of the existing, active events, but must be associated with the same CI.

If Enable Changing State of Related Events is set to true, on receiving a new event, a search is made for related events and any found related event is closed or set to resolved.

• Change State
• Change State of Events Having the Same Key
• Detected Related Events by ETI
• Detected Related Events by Key Matching Pattern
• Enable Changing State of Related Events
• Evaluate "OR" Patterns
• Track Event IDs in Custom Attributes

• Maximum Events

• Enable Content Pack Development

• Available Custom Attributes

• Downtime History Range
• Future Downtime Range
• Refresh Time Interval

A new event can be a duplicate of an existing event. For each new event that is received by OMi, a check is made to establish whether it is a duplicate of an existing (original) event. If the original event is found, the new event is excluded from any further processing and not added to the Event Browser. The original event is updated with information from the new event. The updates include the following information:

• Duplicate count is increased by 1

• Time received is changed to that of the new event

  Note The original time received and the time first received remain available in event history lines.

Optionally, the following updates can also be made:

• Change title to that of new event

• Change severity to one of the following states:

  • Value contained in the new event

  • Most critical value from the new and original severity

• Update custom attributes to those of the new event

Duplicate matching operates as follows:

• If the new event has the No Duplicate Suppression flag set, no search for an original event is made.

• If the new event includes a key, a search is made for an existing, active event that has the same key as the new event, and that are separated by less than the time period specified in the Maximum Age of Duplicate Events setting.

• If the new event does not include a key, a search is made for an existing, active event where a set of configurable attributes have the same values as the new event, and that are separated by less than the time period specified in the Maximum Age of Duplicate Events setting.

• If no original event is found yet, and the new event has an ETI value for a health-contributing ETI, a search is made for an existing, active event that has the same ETI value and the same CI, and that are separated by less than the time period specified in the Maximum Age of Duplicate Events setting.

The number of duplicates received for an event is available in the Event Browser. The Time Received value reflects the time that the latest duplicate arrived. The Time First Received value reflects the time that the event first arrived; the received time is also maintained in the Event History.

The following settings are available for the Duplicate Events Suppression Settings:

• Detect Duplicate Events by ETI
• Detect Duplicate Events by Identical Attributes
• Detect Duplicate Events by Key
• Enable Duplicate Events Suppression
• Generate history lines for Duplicate Event Suppression
• Ignore Existing Events in or after Selected State
• Maximum Age of Duplicate Events
• Select Application
• Select Category
• Select CI
• Select CI Hint
• Select ETI Hint
• Select ETI Value
• Select HPOM Service ID
• Select Node
• Select Node Hints
• Select Object
• Select Policy Condition ID
• Select Severity
• Select Subcategory
• Select SubComponent ID
• Select Title
• Select Type
• Update Custom Attributes of Original Event
• Update Description of Original Event
• Update Severity of Original Event
• Update Title of Original Event

• Cache Clean-Up Interval
• Dynamic Cache Allocation
• Maximum Event Age
• Maximum Event Count

• EPI Server Timeout

• Deny Remote Actions
• Deny Event Actions on Management Server

Lists the available configurations used to customize how closed events are automatically removed from the database and archived to an XML file or a compressed (.zip) file.

• Archive Name

Base Path

To find the value of the default base path for archiving, execute the following command on the data processing server system:

ovpath -ovrg server -datadir archive

Linux default: /var/opt/OV/shared/server/datafiles/archive
Windows default: C:\ProgramData\HP\HP BTO Software\shared\server\datafiles\archive

You can enter an alternative base path. Both absolute and relative paths are accepted, for example:

Absolute: C:\ArchiveFiles
Relative: events/

The specified relative path is appended to the default base path. For example, events/ results in the following base path:

C:\ProgramData\HP\HP BTO Software\shared\server\datafiles\archive\events

• Compress Archive
• Confirmation Event
• Enable Automatic Archiving
• Event Age
• Execution Interval
• Minimum Disk Space
• Proxy Host
• Proxy Port
• Remove entries from all event related tables in parallel to the main event table
• Restrict by Severity
• Storage Type
• Transaction delay
• Transaction size

• Maximum Property Length
• Generate history lines for state changes in pipeline

• Propagation of Assignment Operation to Symptom Events

Propagation of Lifecycle State Operations to Symptom Events

• Disabled but close operation is propagated to symptom events — Lifecycle state changes are not propagated to symptom events except for closing of events.
• Enabled — Lifecycle state changes are propagated to symptom events.
• Disabled but close operation unrelates symptom events — Lifecycle state changes are not propagated to symptom events. Closing the cause event unrelates symptom events.

• Disable Receiving of Events

• Cache Cleanup Interval
• Dynamic Cache Allocation
• Maximum Event Age
• Maximum Event Count

Controls whether events are forwarded to connected servers, the forwarding mode, and the expiration time of forwarding requests.

Event Flow Logging Mode

Writes the logs to the following log files:

Data processing server: <OMi_HOME>/log/opr-backend/opr-flowtrace-backend.log
Gateway server: <OMi_HOME>/log/wde/opr-gateway-flowtrace.log

The advantages of file logging include the possibility to increase the number of logs stored in the log files (by default approximately 700,000 log lines per server) and that you can use alternative tools for viewing the data.

mem writes the most recent 10,000 logs to an in-memory database, which you can access in the JMX console:

https://<data processing server>:29922/mbean?objectname=opr.backend%3Aname%3DEventFlowTraceMBean

In-memory logging automatically combines the event information from all servers and therefore displays the flow of an event in one place. You can also filter the logs to reduce the amount of information displayed.

Event Forwarding Batch Count

Default: 100

Minimum: 1

Maximum: 500

Note If less than the configured maximum number of events or updates are available in the queue, all are sent in one request. Only if more than the configured number are waiting in the queue, are multiple requests created.

For example, if 120 events are in the queue and the default is set to 100, the first 100 events are sent, followed by the remaining 20 events. If only 1 event is in the queue at that moment, that one event is sent.

Event Forwarding Expiration

Default: 12 hours

Minimum: 1 hour

Maximum: 720 hours (30 days).

If the request to forward an event to a particular connected server fails, the request is deleted from the forwarding queue and the event makes an internal note that the delivery to the target server has failed.
The event maintains information about the failed request to the specified connected server. Any further forwarding rule matches on this event for this connected server is ignored. If the forwarding type was set to Synchronize and Transfer Control, a standard event annotation is also added to the event, otherwise no event annotation is made.

Failure to deliver can occur for retry timeouts, or a catastrophic delivery error. A catastrophic delivery error is a situation where it does not make sense to retry the request, for example, a mis-configuration (authentication fails), or a programming error that is encountered in an External Process groovy adapter (NullPointerException). These cases require manual intervention before retrying.

To manually retry failed requests to a particular connected server, from the Event Browser, manually transfer control of an event that has previously failed delivery to a particular server.

• Forward Event Properties as CMAs
• Forward Events
• Ignore incoming CMA deletion from OM
• Incoming Event Acknowledge
• Maximum Steps to Affected Service
• One-line Event Forwarding
• Retry Notify Interval
• Web Service Settings

• Allow Rule Overwrite

Specifies the connection information used to communicate with one management server. These connection settings are used for synchronization of events between and the specified management server.

HPOM Host

It is recommended to specify connections to external servers, including OM management servers, using the Connected Servers manager. For details, see How to create a connection to an OM server.

• HPOM User

• Commit Bulk Size
• Dump Data
• Groovy Scripts
• OM Agent Node Creation Forwarding Targets
• Packages for Topology Sync
• Skip CI Deletion

• Event Count Rule
• Event Subcategories

Specifies the address of the License Reporting Server.

Server Name

Note If no server is specified, no reports are generated.

• Maximum Event Age

• Polling Interval

Specifies the time in seconds after which relative date filters are re-evaluated.

Re-evaluation Interval

Valid range is 30 seconds to 86400 seconds (24 hours).

• Cost Per Event
• Currency
• Enable Cost Saving Calculation

• Forward All
• Forward All Target Server
• Staging Mode Enable

• Illegal Tool Parameters for Commands
• Illegal Tool Parameters for Scripts

Defines the event categories recognized by OMi, for example: Exchange, WebApp, System, or Operating Systems.

• Categories
• Refresh Interval

• CI Centering Mode

Defines how long waits when gathering events before starting the correlation process.

Auto-Extend Time Window Mode

Each time that an event is correlated with a problem, the time period set in the correlation time window is restarted to help enable the correlation of a greater proportion of symptoms associated with the original event.

The correlation time window is only automatically extended when an a new symptom is added to a cause AND the cause is not yet closed. If the cause is already closed, the time window is not extended anymore so that after the last time window elapses, future repetitions of symptoms are no longer correlated to the closed cause.
This avoids ignoring new similar symptoms. Just because a cause is closed, it is not necessarily true that the problem is solved. If the same symptoms continue to occur, they were most likely not caused by the closed cause event and should become visible in the Event Browser.

• Correlate Closed Cause Events
• Correlation Time Window
• Max Query Result Cache Time
• Max Waiting Queue Size

• Group Tools

Maximum Event Count

When in Purge Mode, a confirmation of being in Purge Mode (maximum number of active events than can be displayed in the Event Browser has been reached) is displayed in the information bar.
In addition, it states which events are still displayed based on their time received (all events older than the stated time are purged out). The value is automatically set during deployment and is dependent on the selected deployment option.

Note It is not recommended to change these values.

If the configured maximum is reached, the oldest 10% of the top level events are removed from the cache. When the number of active, top-level events is less than 80% of the maximum value, the purged events are reloaded.

For example, if the default Event Cache Max Level of 20000 is reached, the 2000 oldest events are removed from the cache. As the number of events in the Event Browser drops to 16000, the purged events are reloaded. The settings are per deployment. The same setting is applied to all gateway servers within the same deployment.

• User Interface Update Interval

• Error Response Verbosity
• Maximum Steps to Affected Services
• REST web service session timeout
• Secure Modify

Defines the context menu check properties for creating performance dashboards.

• Breakdown values purging period
• Maximum number of breakdown values

• Default Over-Time Time Period
• Display Business Impact Bar
• KPIs to hide in the report

• Default Non Critical Statuses
• Reports Delay Time

• Changes period

• Number of recent actions
• Show clear recent option
• Show recent menu option

• TQL name for incidents with impact
• TQL name for incidents without impact
• TQL name for requests for change with impact
• TQL name for requests for change without impact

• Connection Failure Timeout
• UI Refresh Rate

• Apply Day Night Overlay Offline Map
• Color Spectrum Offline Map
• Enable export to Google Earth button
• Ignore gray statuses
• Indicator size in Virtual Earth
• Maximum CIs in location tooltip
• Use Virtual Earth
• Wait after getting data

• CI name maximum character length
• Displayed CI limit
• Hierarchy - Default state
• Hierarchy - Number of display levels
• Maximum number of nodes in Topology map
• Neighborhood view depth
• Set CI status to OK until first event occurs

• Sound Notification

• Service Health Tooltip Body Color Property
• Service Health Tooltip Border Color Property
• Service Health Tooltip Font Size

• Custom Background Image Layout
• Custom Background Image Name
• Default Top View Layout
• Hide the view root in Top View
• Independent refresh
• Independent refresh rate
• Initial Number of Levels
• Maximum distance between CIs
• Problematic Subtree Worst status
• Show HIs by default
• Show KPIs by default
• Virtual group size

• Maximum Number of CIs
• Refresh Request Timeout