At this particular beginning of May, Canopsis continues to deliver new things… On the menu for Canopsis V 3.40 : multi-instantiation of engines, display of users’ announcements, and, above all, the awaited new correlation! Follow the guide…
Multi-instantiation of the engines in Canopsis V 3.40
Quick reminder :
• Canopsis Engine-CHE (same pronunciation as the Argentine revolutionary) ensures filtering and enrichment of events.
• Canopsis Engine-AXE handles the alarms.
In previous versions, these engines could only initiate once.
With increasingly high volume to be processed and more and more management rules, our supercar had taken on the appearance of a license-free car in the Ascent of Alpe d’Huez !
Canopsis V 3.40 corrects the situation by allowing its engines to launch several times and simultaneously in the same environment…
Its engines are multi-instantiable !
In concrete terms, what does it allow ?
A much better processing performance, meaning an improvement in the event rates processed on entry (~ 1500 possible events/second circulating in Canopsis).
Note : 1500 events/s = ~450 000 events in 5 minutes, standard frequency of supervision checks… and that’s quite a lot !
High engine availability, if one instance of an engine is no longer running, another takes over immediately, resulting in minimal loss of production… This is what we call « resilience ».
Canopsis is the control tower of the information system and, like the passenger information signs, our solution has a messaging tool.
Messages are programmed in advance and personalized to respond, in particular, to specific color code.
This feature can come in handy during scheduled maintenance, for example.
The correlation in Canopsis V 3.40
The correlation engine has arrived in this new version of Canopsis. We already mentioned it a few weeks ago in an article on our blog: The correlation in Canopsis.
Major tool for limiting the number of alarms in the teams’ processing tray, correlation offers multiple possibilities for rules in Canopsis :
The native parent-child link (component-resource)
If a resource is in alarm state at the same time as the component on which it depends, then a meta-alarm concerning the component is created.
Time grouping »
If alarms appear within a predefined period of time, they will be grouped into a meta-alarm which will then concern a new entity.
Grouping by attributes
If alarms with common attributes appear, they will be grouped into a meta-alarm.
Mix of grouping : « time/ attributes / counters »
Mixing different rules offer a wide range of possibilities.