Feat/notification features

canary-checker/docs/scripting/cel.mdx

@@ -51,6 +51,26 @@ o.a.?d.orValue('fallback value') => 'fallback value'
 
 You can read more about [or](#or) and [orValue](#orvalue) below.
 
+## matchQuery
+
+`matchQuery` matches a given resource against a search query.
+
+Syntax:
+
+```javascript
+matchQuery(r, s)
+
+// Where
+//  r = resource
+//  s = search query
+```
+
+Example:
+```javascript
+matchQuery(.config, "type=Kubernetes::Pod")
+matchQuery(.config, "type=Kubernetes::Pod tags.cluster=homelab")
+```
+
 ## aws
 
 ### aws.arnToMap

common/src/components/Fields.jsx

@@ -23,6 +23,7 @@ const schemes = {
   resourceselectors: '[[]ResourceSelector](/reference/resource-selector)',
   connection: '[Connection](/reference/connections)',
   string: '`string`',
+  "[]string": '`[]string`',
   icon: '[Icon](/reference/types#icon)',
   bool: '`boolean`',
   int: '`integer`',
@@ -37,11 +38,16 @@ function useSchemeUrl(value) {
     return "string"
   }
 
-  value = schemes[value.toLowerCase()]
+  const key = value.toLowerCase();
+  if (!(key in schemes)) {
+    return value;
+  }
 
+  value = schemes[key]
   if (value == null || !value.includes('](/')) {
     return value
   }
+
   // Extract link text and URL
   const matches = value.match(/\[(.*?)\]\((.*?)\)/);
   if (matches) {

mission-control/docs/guide/notifications/concepts/wait-for.mdx

@@ -11,12 +11,11 @@ If alerts are configured for `config.unhealthy` events, these transient state fl
 To address this issue, you can utilize the waitFor parameter.
 This feature allows you to define a delay before sending notifications for specific events.
 After an event occurs, the system rechecks its status following the specified wait period. Only if the undesired state persists does a notification trigger.
+
 :::info
-`waitFor` is only applicable on health related events
+`waitFor` is only applicable to notifications of health related events
 :::
 
-This approach helps reduce unnecessary notifications caused by transient state changes, ensuring you're alerted only to persistent issues.
-
 
 ```yaml title='notify-unhealthy-deployments.yaml' {8}
 apiVersion: mission-control.flanksource.com/v1
@@ -33,9 +32,13 @@ spec:
 ```
 
 :::warning Handling Scrape Lag
-`waitFor` re-evaluates the health based on the current state in config-db, in some circumstances there can be a lag between when a change occurs and the state reflects in config-db which can lead to false positives.
 
-`waitForEvalPeriod` forces an incremental scrape of the resource before sending a notification, it waits for up to this period for a scrape to complete before sending a notification.
+`waitFor` re-evaluates the health based on the current state in config-db. 
+However, in some circumstances, there may be a delay between when a change occurs and when it's refelected in config-db,
+potentially resulting in false positives.
+
+`waitForEvalPeriod` forces an incremental scrape of the resource before sending a notification.
+It waits for up to this period for a scrape to complete before sending a notification.
 
 ```yaml title=waitForEvalPeriod.yaml
 apiVersion: mission-control.flanksource.com/v1
@@ -49,5 +52,29 @@ spec:
   //highlight-next-line
   waitForEvalPeriod: 30s
 ```
+:::
+
+### Grouping Notifications
+
+Multiple related notifications may be generated within a short time window. Instead of sending each alert separately, 
+you can use notification grouping to consolidate multiple events into a single message.
 
+_Example_: When a Kubernetes deployment becomes unhealthy, its replicaset and associated pods will also become unhealthy. 
+If you have a notification set up to alert on `config.unhealthy`, you'll receive 3 different notifications at the very least for the same cause.
+
+The `groupBy` parameter allows you to define how notifications should be grouped. 
+Grouping can be done via 
+- `type` (type of the config)
+- `description`
+- `status_reason`
+- `labels` in the format `labels:app`
+- `tags` in the format `tag:namespace`
+
+:::info
+Grouping only works with waitFor. 
+Hence, a waitFor duration is required 
 :::
+
+
+```yaml title="" file=<rootDir>/modules/mission-control/fixtures/notifications/config-health.yaml {11-12}
+```

mission-control/docs/guide/notifications/index.mdx

@@ -85,6 +85,18 @@ In this example:
 - This expression evaluates to true only when the `type` attribute of the [check](/reference/canary-checker/check) object is equal to `'http'`.
 - So, Mission Control only sends notifications for events that meet this condition, which alerts you when HTTP checks fail.
 
+<details summary="Sophisticated Filters">
+For a more sophisticated filter, you can also use the handy [`matchQuery`](/reference/scripting/cel#matchquery) cel function that supports search query.
+Example:
+
+```yaml title="config.yaml" file=<rootDir>/modules/mission-control/fixtures/notifications/config-health-match-query.yaml {9}
+```
+
+In this example, the filter matches all unhealthy or warning deployments and pods in the prod cluster except for the postgres deployment.
+
+</details>
+
+
 ## Triggering Playbooks
 
 Playbooks can be configured as recipients for notifications, allowing you to trigger automated workflows instead of sending notifications to traditional channels like email or Slack. 
@@ -111,4 +123,4 @@ The example shows two notifications: `check-alerts` and `homelab-config-health-a
 The group has `playbook:run` permission, which both notifications inherit.
 
 ```yaml title="permission.yaml" file=<rootDir>/modules/mission-control/fixtures/permissions/config-notification-group-playbook-permission.yaml
-```
+```

mission-control/docs/reference/notifications/_notification.mdx

@@ -55,6 +55,11 @@
     description: "an additional delay after WaitFor before evaluating Kubernetes config health",
     scheme: "duration"
   },
+  {
+    field: "groupBy",
+    description: "Group notifications that are in waiting stage based on labels, tags and attributes. Only applicable when `waitFor` is provided. See [Grouping attributes](../../guide/notifications/concepts/wait-for#grouping-notifications)",
+    scheme: "[]string"
+  },
   {
     field: "title",
     description: "Channel dependent e.g. subject for email",