Clarify events forwarded to Dynatrace

Signed-off-by: Arthur Pitman <[email protected]>
keptn-contrib · Dec 21, 2021 · d1feaa9 · d1feaa9
1 parent a12b275
commit d1feaa9
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 4 deletions.
diff --git a/README.md b/README.md
@@ -40,7 +40,7 @@ If you are planning to upgrade to dynatrace-service version `0.18.0` or newer fr
   - [SLI provider](documentation/sli-provider.md)
     - [SLIs via `dynatrace/sli.yaml` files](documentation/slis-via-files.md)
     - [SLIs via a Dynatrace dashboard](documentation/slis-via-dashboard.md)
-  - [Forwarding deployment and test events from Keptn to Dynatrace](documentation/event-forwarding-to-dynatrace.md)
+  - [Forwarding events from Keptn to Dynatrace](documentation/event-forwarding-to-dynatrace.md)
   - [Forwarding problem notifications from Dynatrace to Keptn](documentation/problem-forwarding-to-keptn.md)
   - [Automatic onboarding of monitored service entities](documentation/auto-service-onboarding.md)
 - Other topics

diff --git a/documentation/event-forwarding-to-dynatrace.md b/documentation/event-forwarding-to-dynatrace.md
@@ -1,6 +1,11 @@
-# Forwarding deployment and test events from Keptn to Dynatrace
+# Forwarding events from Keptn to Dynatrace
 
-By default, the dynatrace-service assumes that all events it sends to Dynatrace, e.g., deployment or test start/stop events, are sent to a monitored entity that has the following attach rules:
+The dynatrace-service will forward `sh.keptn.event.deployment.finished`, `sh.keptn.event.test.triggered`, `sh.keptn.event.test.finished`, `sh.keptn.event.evaluation.finished`, `sh.keptn.event.release.triggered` and `sh.keptn.event.release.finished` events to Dynatrace by creating the appropriate events in the Dynatrace tenant. For `sh.keptn.event.action.triggered`, `sh.keptn.event.action.started` and `sh.keptn.event.action.finished` events raised as part of a remediation action, it will create information and configuration events if a Dynatrace problem is associated with the event.
+
+
+## Targeting specific entities using attach rules
+
+By default, the dynatrace-service assumes that all events are sent to monitored entities that satisfy the following attach rules:
 
 ```yaml
 attachRules:

diff --git a/documentation/feature-overview.md b/documentation/feature-overview.md
@@ -4,7 +4,7 @@ The dynatrace-service supports the following use cases:
 
 - [**SLI-provider**](sli-provider.md): To support the evaluation of the quality gates, the dynatrace-service can be configured to retrieve SLIs for a Keptn project, stage or service. Two modes are available: [SLIs via a combination of `SLI.yaml` files](slis-via-files.md) located on the Keptn service, stage and project, or [SLIs and SLOs based on a Dynatrace dashboard](slis-via-dashboard.md).
 
-- [**Forwarding deployment and test events from Keptn to Dynatrace**](event-forwarding-to-dynatrace.md): The dynatrace-service can forward events such deployment or test start/stop events to Dynatrace along with attach rules to ensure that the correct monitored entities are associated with the event.
+- [**Forwarding events from Keptn to Dynatrace**](event-forwarding-to-dynatrace.md): The dynatrace-service can forward events such as remediation, deployment, test start/stop, evaluation or release events to Dynatrace along with attach rules to ensure that the correct monitored entities are associated with the event.
 
 - [**Forwarding problem notifications from Dynatrace to Keptn**](problem-forwarding-to-keptn.md): The dynatrace-service can support auto-remediation by forwarding problem notifications from Dynatrace to a Keptn environment and ensuring that the `sh.keptn.events.problem` event is mapped to the correct project, service and stage.