Unified Assurance Topology Cache Warmup Microservice
Overview
The Unified Assurance Topology Cache Warmup microservice is part of the microservice event pipeline. It preloads the topology for a certain set of zones into redis. It runs once as a sidecar when first installing redis, and subsequent runs are not required.
Prerequisites
-
A microservices cluster must be setup. Refer to Microservice Cluster Setup.
-
Redis must be installed. Refer to Redis microservice.
Setup
su - assure1
export NAMESPACE=a1-zone1-pri
export WEBFQDN=<Primary Presentation Web FQDN>
a1helm install topology-cache-warmup assure1/topology-cache-warmup -n $NAMESPACE --set global.imageRegistry=$WEBFQDN
Default Configuration
Name | Value | Possible Values | Notes |
---|---|---|---|
LOG_LEVEL | INFO | FATAL, ERROR, WARN, INFO, DEBUG | Logging level used by application. |
STREAM_INPUT | neo4j:///Graph | Text, 255 characters | Neo4j connection URI. |
STREAM_OUTPUT | redis://redis-master.a1-zone1-pri.svc.cluster.local:6379 | Text, 255 characters | Redis server hostname and port. |
ZONES | "1" | Text, 255 characters | A comma separated list of zones. All zones are preloaded if an empty string is set. |
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 loading all zones
a1helm install topology-cache-warmup assure1/topology-cache-warmup -n $NAMESPACE --set global.imageRegistry=$WEBFQDN --set-string configData.ZONES=""
Example of loading zone id 2
a1helm install topology-cache-warmup assure1/topology-cache-warmup -n $NAMESPACE --set global.imageRegistry=$WEBFQDN --set-string configData.ZONES="2"
Example of loading zone ids 1, 2, 3, 4
a1helm install topology-cache-warmup assure1/topology-cache-warmup -n $NAMESPACE --set global.imageRegistry=$WEBFQDN --set-string configData.ZONES="1\,2\,3\,4"