Skip to content

ssi: add processor tags and preserve_original_event on failure (1/4) - #20572

Draft
kcreddy wants to merge 2 commits into
elastic:mainfrom
kcreddy:tagging-evt-original-standards
Draft

ssi: add processor tags and preserve_original_event on failure (1/4)#20572
kcreddy wants to merge 2 commits into
elastic:mainfrom
kcreddy:tagging-evt-original-standards

Conversation

@kcreddy

@kcreddy kcreddy commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Proposed commit message

Tag every ingest pipeline processor across 51 SSI-owned packages
(1password through entityanalytics_entra_id) with a unique,
descriptive identifier so that failure telemetry can attribute
errors to the specific step that failed rather than collapsing
same-type processors into one bucket.

Add preserve_original_event to pipeline-level on_failure handlers
that were missing it, ensuring the raw payload is retained when a
pipeline error document is indexed.

Updates https://github.com/elastic/integrations/issues/20558

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

Tag every ingest pipeline processor across 51 SSI-owned packages
(1password through entityanalytics_entra_id) with a unique,
descriptive identifier so that failure telemetry can attribute
errors to the specific step that failed rather than collapsing
same-type processors into one bucket.

Add preserve_original_event to pipeline-level on_failure handlers
that were missing it, ensuring the raw payload is retained when a
pipeline error document is indexed.

Updates elastic#20558
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

Update the link field in each new changelog entry from the tracking
issue to the merged pull request.

Updates elastic#20558
@infra-vault-gh-plugin-prod

infra-vault-gh-plugin-prod Bot commented Aug 6, 2026

Copy link
Copy Markdown

💔 Build Failed

Failed CI Steps

History

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

✅ All changelog entries have the correct PR link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant