[SLO] Updated burn rate threshold value is not properly shown in the slo detail page

[mgiota]

🍒 Summary

When I created an SLO burn rate value, I used the default burn rate thresholds (14.4x for the critical case). When I updated the SLO burn rate value (168x in my example), I would expect the updated value to appear in the burn rate widget in the SLO details page.

edit_burn_rate.mov

✅ Acceptance criteria

• The updated burn rate threshold should be displayed on the overview burn rate widget in the slo details page
• The updated burn rate threshold should be reflected on the error rate chart in the slo details page
• The updated burn rate threshold should be reflected on the rule edit page

Note: I didn't test if lookback window gets displayed correctly. If it is not displayed correctly, update description and acceptance criteria.

[elasticmachine]

Pinging @elastic/actionable-observability (Team: Actionable Observability)

[mgiota]

@kdelemme @simianhacker Do we maybe have an issue for this already? I remember @simianhacker mentioning in one of our meetings that error rate chart should read the values from the burn rate rule.

Update: @simianhacker I think this is the one, right?

[simianhacker]

@mgiota Yes... that's the issue

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[paulb-elastic]

This was raised by SRE today when I was on the Synthetics call with them.
It's also evident by editing the burn rate rule - the updated value does not appear when re-opening the rule page (note that looking at the saved object, the value IS updated, but the UI on the rule edit page is not reflecting the new value)

I've added this case to the main description

[paulb-elastic]

It seems that #176317 has fixed the edit rule page problem, but not the SLO details page.

Default rule created (which sets a critical burn rate threshold of 14.40)

Changed this to 16:

Still shows as the original 14.4 on the SLO details page:

[paulb-elastic]

I've removed the bug label I added because of #170605 (comment), which has been fixed.

This issue is slightly different, and the original intent was to show the default burn rates, hence why it does not update.