0.10.2

Release Notes 0.10.2

This release enables better Auto Remediation integrations as the tags from a Dynatrace problem are also added to the Keptn Problem Event which is then accessible by any remediation action handler, e.g: its now possible to use these tags when creating a ticket in Jira, OpsGenie, VictorOps, ServiceNow or other incident management systems

This release also includes a fix when creating Dynatrace Custom Alerts as well as improved logging of problem event handling

New Features

• Dynatrace Problem Event Tags added to Keptn Problem Event #221

Fixes

• Use correct default Dynatrace service error rate metric when setting up alerts #229
• Improved logging when dynatrace-service processes incoming problem events from Dynatrace #223

0.10.1

Additional support for Auto-Remediation by sending Keptn Remediation Workflow Events to Dynatrace Problems

0.10.0

Release Notes 0.10.0

New Features

• Allow to configure which Dynatrace entities are set up #182
• Improved error handling and logging #185
• Allow to skip SSL verification #192
• Auto-import for Service Entities detected in Dynatrace #191

0.9.0

Release Notes 0.9.0

New Features

• Adding the Problem URL of Dynatrace as a label and sending informational and configuration change events for auto-remediation actions #177
• Run distributor as sidecar #175
• Don't exit if API connection check goes wrong #171
• Allow installing dynatrace-sli-service in any namespace #172

Support production readiness

Removed two features since they cannot be performed in a production-like environment.

• Removed check for OneAgent #175
• Removed calculated metric creation #168

0.8.0

Release Notes 0.8.0

This release addresses RBAC issues of the dynatrace-service on a Kubernetes cluster and is adapted to work with Keptn 0.7.

Attention: In this release, the Dynatrace OneAgent Operator will not be installed automatically.

New Features

• Send problem comments when actions are triggered/finished #142
• Added problemUrl to problem payload #144
• Created and now uses RBAC objects #145
• Removed dependency from keptn-domain ConfigMap #148
• Removed the installation of Dynatrace OneAgent when configuring monitoring #156

Fixed Issues

• Correct WebSocket URL to /websocket #152

Known Limitations

• For old limitations, please see Release 0.7.0.

0.7.1

Release Notes 0.7.1

New Features

• No new features

Fixed Issues

• Check availability of credentials during DT setup #137

Known Limitations

• For old limitations, please see Release 0.7.0.

0.7.0

Release Notes 0.7.0

New Features

• Enrich Events sent to Dynatrace with Labels & Source (#116)[https://github.com//issues/116]
• Support multiple Dynatrace environments (for different stages/projects)
• Support non-keptn deployed services (#115)[https://github.com//issues/115]

Fixed Issues

• Only handle cloud-events coming from the Dynatrace tenant (#127)[https://github.com//issues/127]
• Set Dynatrace OneAgent Operator version to 0.6.0 to avoid incompatibilities with older Kubernetes versions (#125)[https://github.com//issues/125]

Known Limitations

• Dynatrace Kubernetes OneAgent operator is now limited to version 0.6.0, which is the last version that supports Kubernetes 1.13 (#132)[https://github.com//issues/132)]
• Prior to 0.7.0, Dynatrace-Service has created an alerting profile with a filter that blocks certain problem notifications. There is a known work-around for this described in (#125)[https://github.com//issues/125]
• Alerting profiles are not overwritten (#134)[https://github.com//issues/134] - also related to (#125)[https://github.com//issues/125]
• When using Container-Optimized OS (COS) based GKE clusters, the deployed OneAgent has to be updated after the installation of Dynatrace

0.6.9

Release Notes 0.6.9

This is re-release of version 0.7.0 which is compatible with Keptn 0.6.1.

New Features

• Enrich Events sent to Dynatrace with Labels & Source (#116)[https://github.com//issues/116]
• Support multiple Dynatrace environments (for different stages/projects)
• Support non-keptn deployed services (#115)[https://github.com//issues/115]

Fixed Issues

• Only handle cloud-events coming from the Dynatrace tenant (#127)[https://github.com//issues/127]
• Set Dynatrace OneAgent Operator version to 0.6.0 to avoid incompatibilities with older Kubernetes versions (#125)[https://github.com//issues/125]

Known Limitations

• Dynatrace Kubernetes OneAgent operator is now limited to version 0.6.0, which is the last version that supports Kubernetes 1.13 (#132)[https://github.com//issues/132)]
• When using Container-Optimized OS (COS) based GKE clusters, the deployed OneAgent has to be updated after the installation of Dynatrace

0.6.2

Release Notes 0.6.2

New Features

• Automated creation of custom alerting events in Dynatrace #1265

Fixed Issues

• Adapted to changes in Dynatrace Dashboard API introduced in Dynatrace Sprint 187 #1387

Known Limitations

• When using Container-Optimized OS (COS) based GKE clusters, the deployed OneAgent has to be updated after the installation of Dynatrace

0.6.1

Release Notes 0.6.1

Fixed Issues

• Fixed the automatic creation of Dynatrace Dashboards #1358

Upgrade instructions

Upgrading from 0.5.x and 0.6.0 to 0.6.1

kubectl -n keptn set image deployment/dynatrace-service dynatrace-service=keptn/dynatrace-service:0.6.1 --record