As an Tazama platform operator,
I want to be able to interact with a running processor,
So that I can issue commands to the processor for operational purposes
And so that I can trigger processor functions independently from the processor's core functionality
Background
At the moment we are only able to interact with a running processor via the trigger payload that triggers the processor's normal behavior, be it to evaluate a transaction, score a typology, or generate a CMS alert. With the advent of NATS and removal of the processors' original RESTful interfaces, there is no convenient mechanism available to talk to a rule processor to give it instructions or get information. Some things that may be useful to do are:
Reinitialize a processor to implement a new network map
Update an application-level variable, e.g. the current logging level
Ask a rule processor to report its configuration template as a JSON schema
Ask a rule processor to report its identity
Ask a rule processor to to respond to a health-check
Acceptance criteria
Determine an efficient way to interact with a running rule processor without compromising platform performance.
Story statement
As an Tazama platform operator, I want to be able to interact with a running processor, So that I can issue commands to the processor for operational purposes And so that I can trigger processor functions independently from the processor's core functionality
Background
At the moment we are only able to interact with a running processor via the trigger payload that triggers the processor's normal behavior, be it to evaluate a transaction, score a typology, or generate a CMS alert. With the advent of NATS and removal of the processors' original RESTful interfaces, there is no convenient mechanism available to talk to a rule processor to give it instructions or get information. Some things that may be useful to do are:
Acceptance criteria