Supervised Event Correlator
The Supervised Event Correlator microservice is part of the RCA3 solution. It takes Supervised Correlation Policies, runs supervised machine learning algorithms, identifies an existing root cause event or creates a new root cause event, and correlates the remaining symptom events to the root cause event.
Supervised Event Correlator Prerequisites
Before deploying the microservice, confirm that a microservice cluster is set up. See Microservice Cluster Setup.
Deploying Supervised Event Correlator
To deploy the microservice, run the following commands:
su - assure1
export NAMESPACE=<namespace>
export WEBFQDN=<WebFQDN>
a1helm install <microservice-release-name> assure1/supervised-event-correlator -n $NAMESPACE --set global.imageRegistry=$WEBFQDN
In the commands:
-
<namespace> is the namespace where you are deploying the microservice. The default namespace is a1-zone1-pri, but you can change the zone number and, when deploying to a redundant cluster, change pri to sec.
-
<WebFQDN> is the fully-qualified domain name of the primary presentation server for the cluster.
-
<microservice-release-name> is the name to use for the microservice instance. Oracle recommends using the microservice name (supervised-event-correlator) unless you are deploying multiple instances of the microservice to the same cluster.
You can also use the Unified Assurance UI to deploy microservices. See Deploying a Microservice by Using the UI for more information.
Changing Supervised Event Correlator Configuration Parameters
When running the install command, you can optionally change default configuration parameter values by including them in the command with additional --set arguments. You can add as many additional --set arguments as you need.
For example:
-
Set the parameters described in Default Supervised Event Correlator Configuration in one of the following ways:
-
Set LOG_LEVEL or one of the redundancy parameters by adding --set configData.<parameter_name>=<parameter_value>. For example, --set configData.LOG_LEVEL=DEBUG.
-
Set CONFIG_CHECK, POLL_LAST, or POLL_TIME by adding --set-string configData.<parameter_name>=<parameter_value>. For example, --set-string configData.CONFIG_CHECK=1200.
-
-
Enable redundancy for the microservice by adding --set redundancy=enabled.
Default Supervised Event Correlator Configuration
| Name | Default Value | Possible Values | Notes |
|---|---|---|---|
| LOG_LEVEL | INFO | FATAL, ERROR, WARN, INFO, DEBUG | Logging level used by application. |
| CONFIG_CHECK | 900 | Integer | Time in seconds between config checks (reading in of new / changed policies). This number should be bigger than poll time. |
| POLL_LAST | 300 | Integer | Time in seconds to check every poll time. This number should not be smaller than the poll time to avoid gaps. |
| POLL_TIME | 300 | Integer | Time in seconds between polls of the event list (and processing of events). |
| REDUNDANCY_POLL_PERIOD | 5 | Integer | The number of seconds between status checks from the secondary microservice to the primary microservice. |
| REDUNDANCY_FAILOVER_THRESHOLD | 4 | Integer | The number of times the primary microservice must fail checks before the secondary microservice becomes active. |
| REDUNDANCY_FALLBACK_THRESHOLD | 1 | Integer | The number of times the primary microservice must succeed checks before the secondary microservice becomes inactive. |
Setting Up Supervised Event Correlator Policies
You can add Supervised Correlation Policies or modify existing Supervised Correlation Policies in the UI. From the Configuration menu, select Events, then select Supervised Correlations. See Supervised Correlations in Unified Assurance User's Guide for more information.
Supported Meta Event Tokens
The following table shows the supported meta event tokens.
| Keyword | Description |
|---|---|
$ACTOR |
Supervised Correlation policy name |
$ACTION |
event-supervised-correlator |
$GROUPBY |
Supervised Correlation policy Group BY value if set. Else empty |
$POLICYID |
Supervised Correlation policy ID |
$POLICYNAME |
Supervised Correlation policy name |
$STARTTIMESTAMP |
Timestamp of first (oldest) event in cluster |
$TIMESTAMP |
Timestamp Meta Event got created / renewed |