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. |
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
Autoscaling¶
For microservice scaling options, please refer to the autoscaling docs.
On top of the standard autoscaling options, this microservice supports the following additional configurations:
| Name | Value | Possible Values | Notes |
|---|---|---|---|
| thresholds.backlogSize | 1000 | Integer | The number of items that need to be in the backlog before the auto-scaling starts additional processes. |
| thresholds.totalEventsProcessed | 400 | Integer | Total events processed by the microservice. If the average of total events processed in five minutes exceeds the threshold, pods will be scaled. |
Example of changing the auto-scaling value¶
To change the thresholds used for this functionality, pass the following to the installation command:
a1helm install ... --set autoscaling.thresholds.backlogSize=2000
Microservice self-metrics¶
The Unified Assurance Event Sink microservice exposes the following self-metrics to Prometheus.
| Metric Name | Type | Description |
|---|---|---|
| total_events_processed | Counter | Number of events processed |
| processing_time_per_event | Gauge | Processing time per event from receiving it to sending it to acknowledging it |
| event_sink_backlog_size | Gauge | Number of items pending in the backlog |