google / google/slo-generator

🐛 [BUG] - use built-in metric to create Latency SLO On Dynatrace

Open
#342 14 comments 0 reactions 1 assignee Claimed by @lvaylet View on GitHub
bug
Dominant language
Python
Stars
564
Forks
88
PR merge metrics
No merged PRs in 30d

Description

### SLO Generator Version

v2.3.4

### Python Version

3.10.11

### What happened?

in the documentation, we're shown using the threshold method with an ext: metric from a OneAgent or ActiveGate extension.

```ext:app.request_latency```
is this mandatory, or can we use built-in metrics like those ones ?

``` builtin:service.response.client```
``` builtin:service.keyRequest.response.time ```

it can be great to add a kind of list of metric that we can use in the documentation :)

### What did you expect?

expected to have a valid result using those two builtin metrics
``` builtin:service.response.client```
``` builtin:service.keyRequest.response.time ```

### Screenshots

```bash
![DESCRIPTION](LINK.png)
```

### Relevant log output

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.