[AO] Add alertDetailsUrl to infra rule types

[maryam-saeidi]

Closes #156534

Summary

This PR adds the alertDetailsUrl to the infra rules. The value of this variable is a link to the observability > alerts page filtered for this instance of alert.

Here is an example of this action variable:

alertDetailsUrl as action variable	Result of action

Note

• I will change this field to kibana.alert.url in another ticket

🧪 How to test

• Ensure that server.publicBaseUrl is configured in kibana.dev.yml
• Create a metric threshold/inventory/logs rule and use the context.alertDetailsUrl in action for this rule
• After an alert is triggered, open the link provided by alertDetailsUrl and make sure that the alert is filtered correctly
• Check the time range, it should be set for 5 mins before the alert start time

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[maryam-saeidi]

/oblt-deploy

[elasticmachine]

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

[crespocarlos]

Infra Monitoring UI LGTM. Just left a non-blocking nit

[jbudz]

ftr_configs.yml

[pmuellr]

We probably want to take the window / look-back into account. Or perhaps rule interval. And consider multiples of those - for example, the range should be 3 x window, or something. If the look-back was an hour, or a day, seeing 5m may not be useful.

We'll probably get additional requirements for this anyway, so deferring till then is probably fine.

[maryam-saeidi]

Good point, I was also thinking about the same but wanted to have a smaller PR focused on generating the link for infra rules for now.
In another instance, I used 1/5 of the alert duration period before the start of the alert and 1/5 after the alert ended (in case it was recovered.)

There is room for improvement, and I created the following ticket to improve this time range:
#158480

[pmuellr]

Had a brief discussion on Slack that we should add some .github/CODEOWNERS magic for the newly added x-pack/test/api_integration/apis/metrics_ui directory, so that PR flagging for these go to the right team.

Other than that LGTM, since there weren't any other ResponseOps changes ...

[benakansara]

LGTM

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: fadca68

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
observability	466	478	+12

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
observability	917.7KB	917.7KB	-18.0B

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
observability	14	15	+1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
observability	45.6KB	46.0KB	+380.0B

Unknown metric groups

API count

id	before	after	diff
observability	472	484	+12

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	19	21	+2
securitySolution	398	402	+4
total			+6

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	20	22	+2
securitySolution	478	482	+4
total			+6

History

• 💚 Build #130009 succeeded 9a8529f
• 💔 Build #129938 failed 86ba4b4
• 💔 Build #129921 failed 77cf960
• 💚 Build #129844 succeeded 135bae0
• 💚 Build #129785 succeeded 04b47b2
• 💔 Build #129708 failed 2e2cd15

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

cc @maryam-saeidi