[RAM] add observability feature for server less

[XavierM]

Summary

FIX => #168034

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[fkanout]

After an initial review with local testing, the rule appeared on Serverless, and it fires alerts. 🎊

[fkanout]

@XavierM, I wanted to check the Alert doc via DevTool, but I couldn't find the index. We are hiding these indices on serverless?

[XavierM]

@XavierM, I wanted to check the Alert doc via DevTool, but I couldn't find the index. We are hiding these indices on serverless?

I will just use .alerts*, that's the simple way.

[mgiota]

@fkanout I see in your screenshot you are testing Custom threshold rule. Based on #167782, shouldn't Custom threshold be disabled on serverless? I am asking, since I want to write some tests for this PR and I want to know, what makes sense to test and what not.

[fkanout]

@fkanout I see in your screenshot you are testing Custom threshold rule. Based on #167782, shouldn't Custom threshold be disabled on serverless? I am asking, since I want to write some tests for this PR and I want to know, what makes sense to test and what not.

@mgiota, that's true, It's disabled by default for serverless. But as this PR is serverless-related only. In order to test it, you need to switch the feature flag on as I did.
The PR is solving the issue that even after turning the feature flag ON, the rule was not appearing.

[fkanout]

also fixes #167053

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[Zacqary]

ResponseOps changes look good

[kdelemme]

Thanks for fixing the active alerts hooks 👍🏻 LGTM

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: fdce9cb

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
observability	488	489	+1

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
@kbn/rule-data-utils	111	112	+1

Async chunks

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

id	before	after	diff
apm	3.7MB	3.7MB	+6.7KB
discover	587.0KB	587.2KB	+195.0B
observability	1.1MB	1.1MB	+101.0B
securitySolution	12.9MB	12.9MB	+756.0B
stackConnectors	525.4KB	525.5KB	+185.0B
triggersActionsUi	1.4MB	1.4MB	+276.0B
total			+8.2KB

Page load bundle

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

id	before	after	diff
apm	38.5KB	36.3KB	-2.2KB
cases	155.0KB	155.2KB	+185.0B
infra	106.7KB	106.9KB	+189.0B
observability	103.9KB	104.1KB	+208.0B
stackAlerts	23.7KB	23.9KB	+186.0B
synthetics	19.4KB	19.6KB	+189.0B
triggersActionsUi	97.0KB	97.2KB	+189.0B
uptime	22.7KB	22.8KB	+188.0B
total			-906.0B

Unknown metric groups

API count

id	before	after	diff
@kbn/rule-data-utils	114	115	+1

ESLint disabled line counts

id	before	after	diff
triggersActionsUi	125	126	+1

Total ESLint disabled count

id	before	after	diff
triggersActionsUi	131	132	+1

History

• 💔 Build #172344 failed 1b259ee
• 💔 Build #172187 failed 0671fe0
• 💔 Build #172069 failed cfb4077
• 💔 Build #172015 failed 424dd97
• 💔 Build #171980 failed 88798dd

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

[mgiota]

@XavierM I think we need to add "observability" under feature_ids in this hook as well:
https://github.com/kdelemme/kibana/blob/b154371821f1ccdcd2336c43b87f41e92517afdf/x-pack/plugins/observability/public/hooks/slo/use_fetch_active_alerts.ts#L81-L85

@XavierM Kevin's valid comment put me into thoughts regarding the feature_ids we pass to other observability rule types. These will need to be changed too, otherwise generated alerts will probably not be displayed in the respective apps on serverless, if my understanding is correct,right?

One example is here apm latency alerts history chart. I can gather the places that need to be changed and fix them. Can you please verify that I need to make changes to rest observability places that specify feature ids? Maybe it is not needed, I need to revisit again how the alert authorization works. I need your input for verification.