Dynatrace Cloud Automation release notes version 256.1.0
Release date: Nov 15, 2022
Dynatrace Cloud Automation version 256.1.0 improves the release validation capabilities with built-in support for the Dynatrace Data Explorer tile and with enhancements regarding configuration as code.
New features and enhancements
Support for visual SLO thresholds
You can specify Pass and Warning criteria for an SLO using thresholds directly in Data Explorer rather than in the tile title.
Implicit SLI and SLO naming using dashboard tile titles
The tile title is used as the display name and a clean version is used as the SLI name.
Tiles that have a title and thresholds defined are considered in a release validation.
Support for the Data Explorer Build and Code modes
- Full
Buildmode with any filter or split-by-clause is supported. - Full
Codemode that includes, for example, arithmetic expressions, is supported.
A single query can have a maximum of 100 metric series (same as for Data Explorer).
Support for custom resolutions in the Data Explorer tile
- Resolutions other than
Infare supported. - If a user-provided query results in more than one value for a metric series, an attempt is made to automatically fix the query (using
resolution=Infor a:fold()transformation). If this attempt fails, an error is returned.
Support for units
Breaking change There is no automatic conversion of microseconds to milliseconds or bytes to kilobytes. To convert between units in SLI files, you need to append a :toUnit(<sourceUnit>,<targetUnit>)transformation to the metric expression.
This breaking change may require adaptations in the dynatrace/sli.yaml files.
- SLI units can be specified in Data Explorer: the previous limitation to
Autofor the unit is removed and the SLI results are converted to the specified unit. Units are consistent among thresholds, tile titles, and the generated SLOs. SLI units can be specified in custom charting tiles.
Improvements for SLIs based on dynatrace/sli.yaml files
- Metrics v2 queries allow a
resolutionparameter. - If a query results in more than one value for an SLI, an attempt is made to automatically set
resolution=Infor a:fold()transformation is performed. - Metrics v2 queries support a
mzSelectorparameter that allows you, for example, to specify a management zone for metrics that have no entity type.
API changes
-
Resource endpoints for retrieving Git resources (for example,
GET /project/{projectName}/resource/{resourceURI}) can't be used with an emptyresourceURIand return an HTTP404error. -
The data model for the Git credentials used in the API endpoints to create and edit projects is more structured. This requires adaptation when used.
Known bugs and workarounds
- A recently discovered issue prevents the use of an Azure Repo as a Git upstream repository of a Cloud Automation project. More precisely, the internally used library
go-git has an open bug that causes client errors when performing Git operations.
References
For a complete list of changes, see the following release notes on GitHub: