Skip to content

Assure1 Event SLM Engine

Overview

The Assure1 Event SLM Engine leverages the configured Service Hierarchies with thresholds and meta events to generate SLM impacted events.

Event SLM Engine Setup

  1. Add Meta Events or modify existing Meta Events:

    Configuration -> Events -> Processing -> Meta Events

  2. 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:

    SLM Service Example

  3. Enable the default Service, unless a specific configuration option is needed.

    Configuration -> Broker Control -> Services

Default Service

Field Value
Package Name coreProcessing-app
Service Name Event SLM Connector
Service Program bin/core/processing/EventSLMEngined
Service Arguments
Service Description Service Level Management Event Correlation Connector
Failover Type Standalone (Supported: Standalone, Primary/Backup)
Status Disabled
Privileged (Checked)

Default Configuration

Name Value Possible Values Notes
CheckTime 900 Integer How often (in seconds) the application checks to see if there are any relevant changes.
LogFile logs/EventSLMEngine.log Text, 255 characters Relative path to Log File.
LogLevel ERROR OFF, FATAL, ERROR, WARN, INFO, DEBUG Logging level used by application.
PollTime 300 Integer How often the engine will analyze the service hierarchies.
PreferIPv4 Enabled Enabled/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 Integer Database shard to be used.
Threads 3 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 needed for advanced administration of the application:

  • Package - coreProcessing-app

  • Synopsis - ./EventSLMEngined [OPTIONS]

  • Options:

     -c, --AppConfigID N   AppConfigID => Application Config ID (Service, Job, or Request ID)
     -?, -h, --Help        Print usage and exit
    
  • Threaded - Multi-Threaded