[SLO] Add a global custom ingest pipeline referenced by all SLO pipel…

[yiannisnikolopoulos]

Release notes

• Custom global ingest pipeline can be configured on SLO rollup data.
• Custom global ingest pipeline can be added on SLO summary data.
• Custom ingest pipeline specific to a SLO can be added for its summary data

Summary

Closes #244386

This PR adds support for global custom ingest pipelines for SLOs, allowing customers to create a single pipeline that applies to all SLO rollup and summary documents.

Changes

New global pipelines:

• slo-rollup-global@custom - Applies to all SLO rollup documents
• slo-summary-global@custom - Applies to all SLO summary documents

New per-SLO summary pipeline:

• slo-summary-{sloId}@custom - Applies to a specific SLO's summary documents (similar to existing slo-{sloId}@custom for rollup)

Pipeline Execution Order

Rollup pipeline: Standard processors → slo-rollup-global@custom → slo-{sloId}@custom

Summary pipeline: Standard processors → slo-summary-global@custom → slo-summary-{sloId}@custom

🔬 How to test

1. Start Elasticsearch and Kibana: yarn es snapshot and yarn start
2. Create an SLO via the UI or API
3. Verify the pipeline includes the new processors:

GET _ingest/pipeline/.slo-observability.sli.pipeline-*
GET _ingest/pipeline/.slo-observability.summary.pipeline-*

Test slo-rollup-global@custom

4. Create the global rollup custom pipeline:

PUT _ingest/pipeline/slo-rollup-global@custom
   {
     "processors": [
       { "set": { "field": "custom.test", "value": "global pipeline works!" } }
     ]
   }

5. Wait ~1 minute for the transform to run, then verify:

GET .slo-observability.sli-*/_search
   {
     "size": 1,
     "sort": [{ "@timestamp": "desc" }],
     "_source": ["custom.rollup_global", "slo.id"]
   }

Test slo-summary-global@custom

6. Create the global summary custom pipeline:

PUT _ingest/pipeline/slo-summary-global@custom
   {
     "processors": [
       { "set": { "field": "custom.summary_global", "value": "summary global works!" } }
     ]
   }

7. Wait ~1 minute, then verify:

GET .slo-observability.summary-*/_search
   {
     "size": 1,
     "sort": [{ "summaryUpdatedAt": "desc" }],
     "_source": ["custom.summary_global", "slo.id"]
   }

Test slo-summary-{sloId}@custom

8. Create a per-SLO summary custom pipeline (replace {sloId} with your SLO ID):

PUT _ingest/pipeline/slo-summary-{sloId}@custom
   {
     "processors": [
       { "set": { "field": "custom.summary_per_slo", "value": "per-SLO summary works!" } }
     ]
   }

9. Wait ~1 minute, then verify:

GET .slo-observability.summary-*/_search
   {
     "size": 1,
     "sort": [{ "summaryUpdatedAt": "desc" }],
     "_source": ["custom.summary_per_slo", "slo.id"]
   }

Note: Existing SLOs created before this change will need to be reset or updated to pick up the new pipeline structure.

[elasticmachine]

Pinging @elastic/actionable-obs-team (Team:actionable-obs)

[elasticmachine]

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

[kdelemme]

LGTM

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: b9b19d8

Metrics [docs]

✅ unchanged

History

• 💔 Build #368504 failed e551699
• 💔 Build #368193 failed f7d867a