EventSLMEngined
The Oracle Communications Unified Assurance Event SLM Engine leverages the configured Service Hierarchies with thresholds and meta events to generate SLM impacted events.
You can run this application as a service using the Services UI.
Event SLM Engine Setup
-
Add Meta Events or modify existing Meta Events:
-
Navigate to the SLM Service Management UI and define a service hierarchy:
Configuration -> Service Management
An additional example of creating a SLM service is available via the documentation:
-
Enable the default Service, unless a specific configuration option is needed.
Default Service
The following table shows the settings for the default service. Actual values are in bold, descriptions of values are in plaintext.
Field | Value |
---|---|
Package | coreProcessing-app |
Name | Event SLM Connector |
Program | bin/core/processing/EventSLMEngined |
Arguments | This field is blank. There is no default value. |
Description | Service Level Management Event Correlation Connector |
Failover Type | Standalone (Supported: Standalone, Primary, Redundant/Backup) |
Status | Disabled |
Privileged | This option is selected. |
See Services in Unified Assurance User's Guide for general information about the settings for services.
See Using Application Primary/Backup Failover for more information about the different failover types.
Default Configuration
The following table shows the default configurations for the application. Actual values are in bold, descriptions of values are in plaintext.
Name | Default Value | Possible Values | Notes |
---|---|---|---|
CheckTime | 900 | An integer | How often (in seconds) the application checks to see if there are any relevant changes. |
LogFile | logs/EventSLMEngine.log | Text, 255 characters | The relative path to the log file. |
LogLevel | ERROR | OFF, FATAL, ERROR, WARN, INFO, DEBUG | The logging level for the application. |
PollTime | 300 | An integer | How often the engine will analyze the service hierarchies. |
PreferIPv4 | Enabled | Enabled or Disabled | IP (either IPv4 or IPv6) of the server that is running the engine. If the server has both IPv4 and IPv6 information, this will be IPv6 unless PreferIPv4 is enabled. |
ShardID | 1 | An integer | Database shard to be used. |
Threads | 3 | An integer | The number of processing threads created. |
Supported Meta Event Tokens
Keyword | Description |
---|---|
$SERVICEID |
SLM Service ID |
$SERVICENAME |
SLM Service Name |
$OPERATOR |
Configured SLM threshold operator |
$STATE |
Service state: 1=Impacted, 2=Recovered (for use as AlarmType) |
$STATE_TEXT |
Service state text 'Impacted' or 'Recovered' |
$IPADDRESS |
IPAddress (either IPv4 or IPv6) of sending server. If device has both IPv4 and IPv6 information this will be IPv6 unless PreferIPv4 is enabled. |
$NODE |
FQDN of sending server |
$THRESHOLD |
Configured SLM threshold value |
$TIMESTAMP |
UTC epoch |
$TIMESTAMP_TEXT |
Long date |
$VALUE |
Raw value compared to threshold |
$WEIGHT |
SLM Filter weight |
Administration Details
The following list shows the technical details you will need for advanced administration of the application:
-
Package: coreProcessing-app
-
Package:
./EventSLMEngined [OPTIONS]
-
Options:
-c, --AppConfigID N AppConfigID => Application Config ID (Service, Job, or Request ID) -?, -h, --Help Print usage and exit
-
Threaded: Multithreaded