Skip to main content

System Operations Impact Notification

Overview​

Properties
Kindnotification:system-ops-impact
WhenA runtime policy detected a non-compliant system on one of the configured triggerEnvironments. Consumer systems operations may be affected by incoming upstream data
Recipient typesConsumer Systems Owners, System Access Control List Developers

Additional configurations​

Environments​

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

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

notifications:
  systemOpsImpact:
    triggerEnvironments: ['production'] # Write the name of the environments in which you would like the notification to be sent

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 mesh.builder.environments.

Skipping conditions​

Configuration 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 ....