At this very special beginning of May, our Open Source hypervision solution continues to deliver new things. On the Canopsis V3.40 menu: multi-instantiation of engines, display of announcements to users and, above all, the famous new correlation! Follow the guide…
Multi-instantiation of engines in Canopsis V3.40
A quick reminder:
- Canopsis Engine-CHE – pronounced [Tché] – filters and enriches events.
- Canopsis Engine-AXE manages alarms
In previous versions, these engines could only instantiate once.
With ever-increasing volumes to be processed and more and more management rules, our supercar took on the appearance of a car without a license as we climbed a mountain!
Canopsis V3.40 now corrects the situation by allowing its engines to launch several times simultaneously on the same environment… Engines are multi-instantiable!
So what does this mean in concrete terms?
- Significantly improved processing performance, i.e. higher throughput of events processed at the input (~ 1500 events/second possible in Canopsis).
Note: 1500 events/s = ~450,000 events per 5 minutes, the standard frequency of supervision checks… and that’s quite a lot! - High engine availability: if one instance of an engine fails, another takes over immediately, ensuring minimal loss of production… We call this resilience.
Announcements
Canopsis is the information system’s control tower and, like passenger information panels, our solution features a message announcement tool.
Messages are pre-programmed and customized to meet specific color codes.
This feature can come in very handy during scheduled maintenance, for example.
Correlation
The correlation engine makes its appearance in this new version of Canopsis. We already mentioned it a few weeks ago in an article on our blog: Correlation in Canopsis.
A major tool for limiting the number of alarms in team processing lists, correlation offers multiple rule possibilities in Canopsis V3.40:
- Relationship rule: Parent / Child
If a resource is in alarm at the same time as the component on which it depends, then a meta-alarm concerning the component is created. - Time window rule
If alarms appear within a predefined period of time, they will be grouped together in a meta-alarm, which will then concern a new entity. - Attribute rule
If alarms with common attributes appear, they will be grouped together in a meta-alarm. - Mixed rule: Time / Attributes / Counters
Mixing the different rules opens up a wide range of possibilities.
In conclusion on Canopsis V3.40…
Canopsis V3.40 brings new features and a higher processing speed… The best thing you can do is try it out!
