The dynatrace-service can support the evaluation of the quality gates by retrieving SLIs for a Keptn project, stage or service in response to a sh.keptn.event.get-sli.triggered event. Two modes are available:
- SLIs via a combination of
dynatrace/sli.yamlfiles located on the Keptn service, stage and project, or - SLI and SLOs based on a Dynatrace dashboard.
The mode selected by the dynatrace-service depends on the value of the dashboard key in the dynatrace/dynatrace.conf.yaml used for a particular event as outlined in Dashboard SLI-mode configuration (dashboard)
To help you understand the queries used for obtaining the SLIs, the dynatrace-service includes a custom query field in each element of indicatorValues in the sh.keptn.event.get-sli.finished event. This consists of the path and query string of the associated API request and is viewable directly in the Event payload in the Bridge.
The dynatrace-service always returns SLIs in the same units as the underlying metric expression. To convert between units, append a :toUnit(<sourceUnit>,<targetUnit>) transformation to the metric expression (e.g. in the Code tab of the Data Explorer). For example, builtin:service.response.time:toUnit(MicroSecond,MilliSecond) will produce a service response time metric in milliseconds. Alternatively, for file-based SLIs, the MV2 prefix may be used to convert microseconds to milliseconds or bytes to kilobytes in a concise way. For example, MV2;MicroSecond;metricSelector=builtin:service.response.time:splitBy():avg&entitySelector=type(SERVICE) will convert the builtin:service.response.time metric from microseconds to milliseconds.
SLIs associated with informational SLOs, i.e. without pass or warning criteria, will be retrieved, however any warnings generated while processing them (e.g. no metric series) will not affect the overall result of the sh.keptn.event.get-sli.finished event.
- The Dynatrace Metrics API provides data with the "eventual consistency" approach. Therefore, the metrics data retrieved can be incomplete or even contain inconsistencies for timeframes within two hours of the current time. Usually, it takes a minute to catch up, but in extreme situations this might not be enough. The dynatrace-service tries to mitigate this issue by delaying SLI retrieval by up to 120 seconds in situations where the evaluation end time is close to the current time.