richard-churchman
5f6bbe45f7
Major bug fixes relating to the Redis implementation in Reprocessing and Search Key Cache were identified and fixed as part of the rekeying development. Included functionality to stop the Exhaustive training. Fixed the Unsupervised learning functionality in Exhaustive Training. Embedded the Mock Data CSV data into a class to make it compatible with Docker without needing to modify the Dockerfile (i.e, build). Included a new table that stores training data to enhance support capabilities for Exhaustive. Reintroduced and validated the Multitenancy functionality. Postgres is now fully deprecated in place of Redis for cache, and all implementations of the Interfaces for Postgres have been removed. No migrations exist to support this deprecation, and Postgres as a cache is now wholly unsupported. Removed the Indexing background thread, as Redis does not require it, given that it is a key-value pair database. Created a RedisCommandFlag Environment Variable to support Fire and Forget write to Redis in Invocation. Implemented functionality to Export, Peek and Download configuration environments using a secure, encrypted scheme. Created a permission to access the functionality via the user interface. Extensive database-based logging is included to provide for a comprehensive audit. Created functionality to Import the encrypted Export file inside a database transaction to ensure consistency. As Docker is now the primary deployment model, log4net instantiation has been moved to an approach that primarily uses programmatic instantiation of the ConsoleLogger and RollingFileAppender given Environment Variables. Implemented functionality to support remote \ mounted Log4Net XML Serialisation files for more advanced log4net configurations. Reintroduced access to counters via the user interface and created a permission. Took the opportunity to implement ReSharper linter suggestions. Disabled the Lock button across the whole application, with that functionality being reserved for future use. It is intended that locking happens programmatically on the basis of dependencies in future commits. Fixed several significant end-use bugs which became apparent during testing of the refactored code relating to case management and visualisations. Fixed certain other minor bugs that came up during testing. Brought documentation up to date for this commit. Brought the Docker Compose file up to date for this commit. Removed Redundant Environment Variables for this commit. Made the README file less verbose and unnecessary.
4.3 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Activation Watcher | 16 | Models | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Activation Watcher
The purpose of the Activation Watcher is to provide a real time ticker of Response Elevations, subject to the Activation Rule having been set to send messages to the Activation Watcher.
The Activation Watcher is available in a main menu item:
Navigate to the Watcher by clicking the menu item:
Ensure that the Real Time mapping check-box is checked to allow plotting on a real-time basis, rather than only relying on solely on Replay:
The Map Entity Once switch exists to ensure that for the key (which would have been defined in the Activation Rule definition) that a flag may only be plotted the once on a map for that key, so not to over-plot the map:
To configure an Activation Rule to dispatch real time messages to the Activation Watcher, navigate to the Volume1DayUSDForIPOver100 for editing:
Scroll down to the Response Elevation section:
Check the Send to Activation Watcher Switch to expose further options:
The fore colour and back colour is the colouring that will be included in the Activation Watcher for the entry tick. The Activation Watcher has the ability to plot on a map, along with the background colour specified. The plotting of activation rule matches on the map relies on a Latitude and Longitude having been specified in the Request XPath or the Inline Script attributes, else it will plot [0,0] (just off Central Africa).
Update the model to Send To Activation Watcher alongside some tasteful colouring:
Scroll down and click update to create a new version of the Activation Rule:
Navigate to the Watcher. Synchronise the model via Entity >> Synchronisation and repeat the HTTP POST to endpoint https://localhost:5001/api/invoke/EntityAnalysisModel/90c425fd-101a-420b-91d1-cb7a24a969cc for response as follows:
There will be nothing of note in the JSON response payload. Note that the pin has been plotted based on a latitude and longitude sent to the watcher.
In this example the Latitude and Longitude is passed in the JSON transaction message:
With the values being specified as being of Data Type Latitude and Longitude in the Request XPath definition, respectively:
The Activation Watcher will only tick through alerts as they happen when that page is connected.
The Replay functionality of the Activation Watcher - but only if the engines have been configured to store Activation Watcher entries in the database - will query and replay these entries through the Activation Watcher as if they were being sent in real-time.
Activation Watcher replay, is for a given date range, in ascending date order, for a maximum of 10000 records, as if they were streaming in real-time. It should not be used to drive workflow, rather be considered a sample.
Set the date range to a day apart:
Before clicking the Replay button, it is recommended to turn off real time ticking, as this will eliminate confusion between real time data and replay data:
To replay, simply click the Replay button, lending a wide date range in this example:
Keep in mind that the map is set to plot an Entity the once, only the grid and the chart will show real activation frequencies:
There are several mechanisms that stop the Activation Watcher being flooded with data and causing the system to become unresponsive. It follows that the Activation Watcher should be viewed to be a sample of activity for a period of time, rather than a system of record or alert.