System Ops Impact Notification

Overview

Properties
Kind	notification:system-ops-impact
When	A runtime policy detected a non-compliant system on one of the configured triggerEnvironments. Consumer systems operations may be affected by incoming upstream data
Recipient types	System Access Control List, Consumer Systems Owners
Modules	ControlPlane
Trigger topics	governance.runtime-policy-failed

Additional configurations

Environments

To let witboost inform users about a system ops impact, you need to configure the set of environments that fires this notification.

This can be done in your values.yaml by adding the following lines under the notifications section at the root level:

# inside your values.yaml
ui:
  appConfig:
    # ... other configurations  ...
    notifications:
      systemOpsImpact:
        triggerEnvironments: ['production']

The name of the environments should match any of the environments configured in your witboost installation. It should be one or more items listed under ui.appConfig.mesh.builder.environments.

Skipping conditions

Configuration ui.appConfig.notifications.systemOpsImpact.skipIfAlreadyNonCompliant determines whether to skip sending the notification if the resource has remained non-compliant with the policy continuously since the last notification was sent:

• if set to none (default): no skipping occurs, and a notification will be sent on each policy failure
• if set to all: the notification will be skipped if the resource is already marked as non-compliant, regardless of the type of policy violation
• if set to dataContractsOnly: the notification will only be skipped if the policy violation is specifically for a data contract

JSON Schema

Loading ....