cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Configure SLO on specific key request, instead of that service as-a-whole

Anyway I can configure SLO on specific key request, instead of that service as-a-whole?

 

Best Regards,

Wai Keat

7 REPLIES 7

Yosi_Neuman
Champion

Hi @waikeat_chan 

You can add filter to the metric to to pick the key request you are looking for.

Yosi_Neuman_0-1615126055776.png

The filter will look something like:

builtin:apps.other.keyUserActions.count.osAndApdex:filter(eq(dt.entity.device_application_method,"DEVICE_APPLICATION_METHOD-B60A00B9A3831556")):splitBy(dt.entity.device_application_method):sum:auto

More information about filter transformation can be found in documentation 

HTH

Yos 

dynatrace certificated professional - dynatrace primer partner - Matrix Soft Ware Division - Israel

The_AM
Dynatrace Pro
Dynatrace Pro

Hi Wai Keat,

Yes, this is possible. It doesn't even need to be a request marked as key request. It just needs to be a metric.
For this you can create a calculated service metric (from the service, click on the chart option for the request, then 'create metric' from the multi-dimensional analysis view).

There's actually a walkthrough that makes this use case as an example in the "Getting Started with SLOs in Dynatrace" performance clinic webinar. You may watch this explanation either within Dynatrace University or on Youtube.

Starts from 26min mark if you're in a hurry

 

Hope that helps.



Andrew

Regards,
Andrew M.

The only concern with creating metrics is that customers do care about their DDU's license that creation of metrics do consume, while creating key user action and using built in metric is free of DDU charge. 

Yos 

dynatrace certificated professional - dynatrace primer partner - Matrix Soft Ware Division - Israel

Hi @The_AM 
The new features is not the same as the one used in the University, we lost a lot of parameters...

 

Can we have details about how we can create the same SLOs shown in the videos with the actual features?

 

Thanks

Sharing Knowledge

nick_hurt
Dynatrace Supporter
Dynatrace Supporter

To add further to this,

 

Calculated service metrics can be created using conditionals on request name or request type (among others). A calculated service metric can then be used as a single metric or included as the numerator/denominator for SLO creation.

james_moriarty
Visitor

This needs to be better documented as is standard SLO/SLI practice. We've managed to get it working but found it was incompatible with the "SLO filter" when using calc service metrics. We also couldn't filter by status code without a calc service metric:

e.g. Latency SLI

<custom success metrics/filter service, endpoint, availability, and latency>
/
builtin:service.keyRequest.count.server:filter(eq("dt.entity.service_method","SERVICE_METHOD-XXX"))

**EDIT**

e.g. Availability SLI

builtin:service.keyRequest.errors.server.successCount
/
builtin:service.keyRequest.count.server

SLO filter: type("SERVICE_METHOD") AND entityId("SERVICE_METHOD-XXX")

cc/ @wolfgang_heider 

wolfgang_heider
Dynatrace Guide
Dynatrace Guide

Thanks a lot for the feedback!
I already triggered to improve docs with your help/feedback/examples
and we think about how to make the filtering more self-explanatory.
The SLO filter would apply for both metrics and for the custom calc metric, there is only the dimension of the service.
This will change with a new query syntax for metrics (coming along with calculated metrics), which will also be part of the SLO setup then. There it becomes more clear, what is possible (to filter) on the individual metric queries and makes the overall setup easier.