Assure1 Javascript Generic Event Processor microservice¶
Overview¶
The Assure1 JavaScript Generic Event Processor is part of the microservice event pipeline. The microservice is responsible for enrichment/processing of custom JavaScript rules-based events and for forwarding them down the event pipeline to a selected target (preferably an event-sink).
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 js-generic-event-processor assure1/js-generic-event-processor -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 *Not configurable yet | persistent://assure1/event/js-generic-processor | Text, 255 characters | Apache Pulsar topic path. Topic at end of path may be any text value |
| STREAM_OUTPUT *Not configurable yet | persistent://assure1/event/sink | Text, 255 characters | Not configurable at this time |
| PRODUCTION_ENV | true | true,false | If true, application WILL NOT display any console.log statements from js rules |
| STRICT_COMPILE | true | true,false | If true, application will force javascript strict compilation rules |
| RULES_LOCATION | /core/default/processing/event/js-generic-event-processor | Text, 255 characters | Default SVN location (within Assure1) for base.rule.js rules processing file |
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