Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[E2E test] Ingesting data with OTel-based shipper pipeline #5016

Closed
2 tasks
ycombinator opened this issue Jun 27, 2024 · 1 comment
Closed
2 tasks

[E2E test] Ingesting data with OTel-based shipper pipeline #5016

ycombinator opened this issue Jun 27, 2024 · 1 comment
Labels
Testing

Comments

@ycombinator
Copy link
Contributor

Background

We are looking into replacing our current Beats sub-process-based data ingestion and shipping architecture with an in-process one based on the OTel Collector. As we do this, we need to ensure that ingesting and shipping data using the new architecture has parity with the current architecture.

Definition of done

  • An E2E test using the new architecture, ingesting data from a log file with N lines, indexing it into Elasticsearch, and ensuring that N corresponding documents are indexed.
  • A similar E2E test for metrics data.
@ycombinator
Copy link
Contributor Author

@cmacknz @pierrehilbert I think we can close this one out as a duplicate of https://github.com/elastic/ingest-dev/issues/3489?

@cmacknz cmacknz closed this as completed Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ycombinator @cmacknz