Enrichment

The enrichment engine adds information to the incoming event:

• By the raw information provided by the event itself
• Via “asynchronous” querying of an external repository
  External source APIs can be used to enrich the Canopsis repository by querying the entire database.
• Via “on-the-fly” querying of an external repository
  APIs can also be used to optimize data storage by querying the repository for a specific element. Ideal for cloud applications!

Here, for example, is some information that the enrichment engine can add:

• 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?

For more information on the enrichment engine and all the other features, see thededicated article and the Canopsis documentation.

✅ Update 2025: External enrichment data

Event filter rules now allow alarms and alarm entities to be enriched via external data sources.

The feature enables these to be managed from the Canopsis graphical interface.

✅ Update 2025: Traceability of enrichments

You can now easily view all the event filter rules applied to an alarm.

This new feature gives you an in-depth understanding of how alarm data has been processed, enriched and modified throughout its journey through the system.

It helps you analyze the conditions that led to the alarm’s final state.

To access enrichment traceability, simply go to the relevant alarm in Canopsis, then click on the section dedicated to event filters. This allows you to examine the various enrichment and event filter steps that have been carried out.