[OMAlerts] Alert Mechanism Supported by Openmetadata

[mohityadav766]

Currently, OM supports the Alert mechanism consisting of the following 3 main components/steps:-

1. Trigger - All / Specific Data Asset (Table, Dashboard, Topic etc)
2. Filtering Mechanism:- Based on SPEL Expression following are the different Expressions available:-
   "matchAnySource" -> Allow to control based on the origin of the event (Table, Topic etc)
   "matchAnyOwnerName" -> Allow/deny data-asset through filtering based on the owner entity that get an update or change
   "matchAnyEntityFqn" -> Allow/deny data-asset through filtering based on the FQN of the entity that gets an update or change
   "matchAnyEntityId" -> Allow/deny data-asset through filtering based on the Id of the entity that gets an update or change
   "matchAnyEventType" -> Allow/deny data-asset through filtering based on type of change(entity_created, entity_updated , entity_deleted, entity_soft_deleted)
   "matchTestResult" -> Applicable for test Cases only to filter specific test case result
   "matchUpdatedBy" -> Filter based on the user who caused the change event
   "matchIngestionPipelineState" -> Applicable for only IngestionPipelines, filtering for status for pipeline
   "matchAnyFieldChange" -> Filter based on specific fields for an entity (name, usage summary etc)
3. Subscriptions -> Slack, MsTeams, Webhook, Email, GChat, etc.

Currently, as we see this level of filtering can be confusing since each filter tends to a specific filtering needs, hence would like to get more inputs for what the community's needs are, what works and what does not.