Package be.cylab.mark.activation

Interface Summary

Interface	Description
ActivationControllerInterface<T extends Subject>
DatastoreFactory
ExecutorInterface	The actual detection jobs can be executed by any platform that implements this interface.

Class Summary

Class	Description
ActivationController<T extends Subject>	The activation controller uses the micro batching principle: https://streaml.io/resources/tutorials/concepts/understanding-batch- microbatch-streaming Events are continuously collected (with notifyRawData and notifyEvidence).In a separate thread, every few secondes (defined by Config.update_interval), analysis jobs are triggered.
ClientWrapper<T extends Subject>	A wrapper around the datastore client code that performs some additional tasks before reading / writing data or evidences to the datastore.
DefaultDatastoreFactory
DetectionAgentContainer<T extends Subject>	Container for running a detection agent.
IgniteExecutor	Allows to run our detection jobs using an Apache Ignite cluster.
JsonRequestListener	Used to track requests performed by the client, so we can keep track of data used by the different detection algorithms.
ThreadsExecutor