[Metrics UI] Add back context variables with descriptions

[phillipb]

Summary

Add back the old context variables with clearer names and descriptions. Fixes: #65974.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[phillipb]

@elasticmachine merge upstream

[sorantis]

@phillipb From the user's perspective it's not clear that each of these context variables is followed by conditionN. Some users reported the following output, which indicated that they didn't use these variables correctly.

alertid:c6b3c440-5d14-49be-bc16-9dae92386ffe
alertName:test
spaceId:default
tags:test
alertInstanceId:304ef5a3-a6b9-4ee3-8ffb-8e2742bd3a7b-hayate
context.group:test
context.valueOf:[object Object]
context.thresholdOf:[object Object]
context.metricOf:[object Object]

Can we clarify it somehow? Maybe by default add condition0 to each context variable as soon as the user clicks on the dropdown? Thoughts?

[phillipb]

@sorantis yeah, I added this issue to address that #67396. It's now added to 7.9 as a documentation fix.

Because the number of conditions is dynamic and the context variable list is static, not sure how we could create a better UX. We could hardcode some values in the context for example ctx.value.condition0, ctx.value.condition1, but that would fail if there were only one condition.

Unfortunately, we don't control the context variable dropdown, so we can't change what's inserted in the message when a user clicks a variable.

[sorantis]

By all means we should update our docs. I'm wondering if there's any way we could put this information on the UI too. It feels like the docs will be helpful only after the user has already struggled with making it work :)

[phillipb]

@sorantis we could link to think docs from the flyout maybe? We could also file an issue with kibana-alerting to see if they have thoughts or plans around this.

[phillipb]

@elasticmachine merge upstream

[phillipb]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: bfe8092

History

• 💚 Build #50858 succeeded ca0b800
• 💛 Build #50784 was flaky 3974bee
• 💚 Build #50078 succeeded 3752dc3
• 💔 Build #50047 failed 51e2f74

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[Zacqary]

Good to go

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 67487 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 67487 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 67487 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 67487 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 67487 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 67487 or prevent reminders by adding the backport:skip label.