Enrichment actions are used to add information to an event or entity, through an incoming event. What are the possibilities of these famous actions? How does this translate into your Canopsis? Well, that’s what we’re going to find out today!
Hypervision enrichment actions: what are they?
Basis of the approach
First, let’s look at what enrichment is.
With this in mind, let’s assume that an event uploaded to the platform is “poor”.
The Enrichment engine in Canopsis, or in any hypervision tool for that matter, must be able to enrich this raw IS information with multiple factors.
For example:
- Importance – How severe is the event?
- Impact – How many users are affected?
- Location – Where is the equipment involved?
- Others – How do I categorize a created alarm? What is the associated instruction? …
Three categories of enrichment
There are also different ways of enriching an incoming event:
- By the raw information provided by the event itself
- Via an “asynchronous” query of an external repository
- Via “on-the-fly” interrogation of an external repository (API)
The 6 enrichment actions in Canopsis
Post-eventfilter event enrichments
Entities enrichments
In conclusion, the six enrichment actions presented already enable you to considerably transform incoming events… but the Canopsis team has no intention of stopping there! Want to find out more about enrichment actions? On the possibilities of Canopsis in general? Go to documentation and demo. Our team of experts is also at your disposal!
