SRG - measure unit inherited when building SLO via DQL

[y_buccellato]

I'm building SLO vi DQL, skipping the standard SLO creation.
When I do so, I have the result in percentage but the result itself is expressed in the original unit for which the metric is calculate upon (millisecond).

How can I force the unit to change: not making it visibile or switch it with the symbol of a percentage?

Regards

[Gerhard-K]

Hi @y_buccellato ,
as you're working in notebooks, you'd probably have to make the notebook section aware of what unit you expect in the results. You can do that in the section options, units&formats.

My bad, just recognized that you're querying your objective within a guardian. Here, I'm afraid, there's no option to change this - I'll doublecheck with the team.

In any case, the result is correct; it seems the guardian's objective is just wrongly taking the unit of the first queried metric, but we will change the unit visualization.

As you are creating SLO based on DQL queries - have you already seen the recently released SLO feature: SLOs for all data types where you can build SLOs based on DQL. In this blog post there's a link to our playground tenant where some SLO examples are presented.

Best,
Gerhard

[y_buccellato]

Thank you Gerard, so far I understood the behavior of DT in SRG, inheriting the unit of measure from the metric I'm using.  Hope I can change the unit soon in SRG as the information applied with DQL make it become a percentage.

Do you know if I can already change this in DQL in notebook for example?
When I first run this query in Notebook it didn't appear to me that the result was inheriting the unit of measure. Also in Data explorer (I did this too with Metric Expression) the metric built seemed to be agnostic to unit of measure.

The SLO new app I must say, I just touched it yesterday and thing are not very good in the fundamentals:

• for example I'm an admin and I cannot access it by default, instead I should create a separate IAM policy
• If I pasted my DQL query there it appears the new SLO app is expecting a different shape of DQL.
  When error happened I tried to click on the link to the feedback channel:
  but this just brought me to the general community page and I decided to go classica SLO cause I was not so acquainted with the new feature.
  
  I don't know if it is in your road map, but you should offer a conversion toggle from Classical SLO to newest if possible.
  
  Best of luck and regards

[Gerhard-K]

The team is already investigating how to address the display of units within the SRG objectives.

You can't change the unit itself in DQL. But, Notebook and Dashboard provide an option to override the displayed unit.

Thanks for the feedback regarding the new SLOs.

• The community link will be updated to forward the user to this page: Feedback channel for the new service-level objectives app - Dynatrace Community
• Regarding the policies—yes, you're right—I'll double-check the admin/new policy flow.
• The SLOs expect a specific result: a time series named "sli" of type array of type "double" to calculate the aggregated SLO status, error budget, and burn rate.
• An upgrade Guide is already planned to allow an easy migration from existing classic SLOs to the new SLOs on Grail.

Thanks

Gerhard