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.

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

E2E Testing for Vector #823

Open
mjnagel opened this issue Sep 25, 2024 · 0 comments
Open

E2E Testing for Vector #823

mjnagel opened this issue Sep 25, 2024 · 0 comments
Labels
ci Issues pertaining to CI / Pipelines / Testing enhancement New feature or request logging Issues related to the Logging stack (Loki/Promtail)
Milestone

Comments

@mjnagel
Copy link
Contributor

mjnagel commented Sep 25, 2024

E2E testing for Vector should only be run on the all package test only since it focuses on interactions between components - see #211 for some thoughts on this.

Initial thoughts on testing areas:

  • Input handling: Ensure that Vector is picking up the expected files (pod + node logs), possibly via the API?
  • Output handling: Ensure that Vector is able to ship to the destinations, possibly via the API or a test with Vector connected to MinIO and checking bucket contents?
  • Other testing: This is not super well defined but we should evaluate if there are other health endpoints or metrics that would be helpful to look at

Vector's API is not enabled by default so we may need to enable it in CI at minimum and use it to access some of these data points.

@mjnagel mjnagel added enhancement New feature or request ci Issues pertaining to CI / Pipelines / Testing logging Issues related to the Logging stack (Loki/Promtail) labels Sep 25, 2024
@mjnagel mjnagel modified the milestones: 0.29.0, 0.30.0 Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Issues pertaining to CI / Pipelines / Testing enhancement New feature or request logging Issues related to the Logging stack (Loki/Promtail)
Projects
None yet
Development

No branches or pull requests

1 participant