Skip to content

Conversation

@taylor-swanson
Copy link
Contributor

@taylor-swanson taylor-swanson commented Dec 9, 2025

What does this PR do?

  • Add validation rule SVR00008 to verify all ingest pipelines set event.kind to pipeline_error in the global on_failure handler.
  • Add validation rule SVR00009 to verify all ingest pipelines set error.message in the global on_failure handler and that the failing processor type, tag, message, and pipeline are included in the error message.

Checklist

Related issues

  • Relates elastic/integration-experience#390

- Add validation rule SVR00007 to verify all ingest pipelines set event.kind to
pipeline_error in the global on_failure handler.
- Add validation rule SVR00008 to verify all ingest pipelines set error.message
in the global on_failure handler and that the failing processor type, tag, message,
and pipeline are included in the error message.
@taylor-swanson taylor-swanson self-assigned this Dec 9, 2025
@taylor-swanson taylor-swanson added the enhancement New feature or request label Dec 9, 2025
@taylor-swanson
Copy link
Contributor Author

/test

@taylor-swanson taylor-swanson marked this pull request as ready for review December 11, 2025 20:03
@taylor-swanson taylor-swanson requested a review from a team as a code owner December 11, 2025 20:03
teresaromero
teresaromero previously approved these changes Dec 15, 2025
Copy link
Contributor

@teresaromero teresaromero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@mrodm mrodm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding the support to validate ingest pipelines defined in the package root. Added a couple of minor comments.

pipelineFileMetadatas = append(pipelineFileMetadatas, pipelineFileMetadata{
filePath: file,
fullFilePath: fsys.Path(file),
dataStream: d.dataStream,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this dataStream field form pipelineFileMetadata struct used ?
Taking a look at #1010 and this PR, it looks like it is not. Could you check it? If not, should it be kept or used somewhere?

Copy link
Contributor Author

@taylor-swanson taylor-swanson Dec 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I haven't used the dataStream field yet, I've added it to keep it consistent with listFieldsFiles and fieldFileMetadata, which is what this function and struct were based on.

return nil, fmt.Errorf("cannot read pipeline files from integration package: %w", err)
type pipelineDirMetadata struct {
dir string
dataStream string
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe if dataStream field from pipelineFileMetadata can be removed, this one too could be removed.

@mrodm mrodm mentioned this pull request Dec 22, 2025
2 tasks
@teresaromero
Copy link
Contributor

@taylor-swanson i merged #1042 and used some codes as yours. please update the pr to resolve conflict. thnks!

@taylor-swanson
Copy link
Contributor Author

@taylor-swanson i merged #1042 and used some codes as yours. please update the pr to resolve conflict. thnks!

Not a problem, will get that fixed up!

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @taylor-swanson

Copy link
Contributor

@teresaromero teresaromero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@teresaromero teresaromero merged commit f615cbe into elastic:main Jan 12, 2026
3 checks passed
@taylor-swanson taylor-swanson deleted the feat/validate-on-failure branch January 12, 2026 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants