You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.
If an external tool, e.g: Jenkins, GItLabs Pipelines ... is doing the deployment and sends a deployment-finished event to Keptn it typically enriches it with e.g: Pipeline URL, GitCommit, ... by passing these values as labels
Users have asked to promote these labels to the corresponding Dynatrace Deployment EVent.
Therefore we suggest to look at all incomgin labels and re-use them for the sent deployment event to dynatrace. For labels such as deploymentName, deploymentVersion, ciBackLink, remediationAction the Dynatrace SErvice should forward them as exactly these propoerties. For all other labels just pass them as customProperties
If an external tool, e.g: Jenkins, GItLabs Pipelines ... is doing the deployment and sends a deployment-finished event to Keptn it typically enriches it with e.g: Pipeline URL, GitCommit, ... by passing these values as labels
Users have asked to promote these labels to the corresponding Dynatrace Deployment EVent.
Therefore we suggest to look at all incomgin labels and re-use them for the sent deployment event to dynatrace. For labels such as deploymentName, deploymentVersion, ciBackLink, remediationAction the Dynatrace SErvice should forward them as exactly these propoerties. For all other labels just pass them as customProperties
sample - incoming keptn depoyment event
that would translate into a Dynatrace Event like this
This enhancement in combination with #115 gives our users full flexibility
The text was updated successfully, but these errors were encountered: