Event Sink
Overview
The Unified Assurance Event Sink microservice is part of the microservice event pipeline. The Event Sink is responsible for taking events that have been normalized and inserts them into the Event database.
Prerequisites
-
A microservices cluster must be setup. Refer to Microservice Cluster Setup.
-
Apache Pulsar must be installed. Refer to Apache Pulsar microservice.
Setup
su - assure1
export NAMESPACE=a1-zone1-pri
export WEBFQDN=<Primary Presentation Web FQDN>
a1helm install event-sink assure1/event-sink -n $NAMESPACE --set global.imageRegistry=$WEBFQDN
Default Configuration
Name | Value | Possible Values | Notes |
---|---|---|---|
DATABASE.ONDUPKEY | Count = Count + 1, Duration = VALUES(LastReported) - FirstReported, EventCategory = VALUES(EventCategory), LastChanged = VALUES(LastChanged), LastReported = VALUES(LastReported), Severity = VALUES(Severity), Summary = VALUES(Summary) | Text, 255 characters | Any valid MySQL ON DUPLICATE KEY UPDATE clause. |
LOG_LEVEL | INFO | FATAL, ERROR, WARN, INFO, DEBUG | Logging level used by application. |
STREAM_INPUT | persistent://assure1/event/sink | Text, 255 characters | Apache Pulsar topic path. Topic at end of path may be any text value. |
STREAM_OUTPUT | mysql:///Event | Text, 255 characters | Not configurable at this time. |
backlogSize | 1000 | Integer | The number of items that need to be in the backlog before the auto-scaling starts additional processes. |
Configurations can be changed by passing the values to the a1helm install
prefixed with the configData parent key.
Example of setting the log level to DEBUG
a1helm install ... --set configData.LOG_LEVEL=DEBUG
Example of changing the auto-scaling value
Auto-scaling is enabled by default. To change the thresholds used for this functionality, pass the following to the install command:
a1helm install ... --set autoscaling.thresholds.backlogSize=2000