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

Add tests to check data ingestion in tobs #324

Closed
VineethReddy02 opened this issue Apr 29, 2022 · 3 comments · Fixed by #564
Closed

Add tests to check data ingestion in tobs #324

VineethReddy02 opened this issue Apr 29, 2022 · 3 comments · Fixed by #564
Assignees
Labels

Comments

@VineethReddy02
Copy link
Contributor

As currently, tobs includes all the components i.e. Prometheus, Otel collector, and Promscale that are required to test the ingestion, and querying of data.

As part of this issue add nightly tests to make sure the recommended config with the latest Otel-collector, Prometheus and Promscale works as expected with data ingestion of metrics and traces.

@paulfantom
Copy link
Contributor

paulfantom commented Apr 29, 2022

Slack discussion was not about adding nightly tests, but about adding nightly release channel for promscale (which is a blocker for this task) and then e2e testing if ingestion through otel-collector works.

Prerequisites for starting this task:

DoD:

  • prometheus is configured to send traces to promscale via otel-collector
  • e2e test suite checks if all components of the stack are up and running
  • e2e test suite checks otel-collector is able to forward data
  • e2e tests are run on every merge to master

What is NOT required:

  • setting up nightly testing channel.

@paulfantom paulfantom added the enhancement Improvement of an existing feature label Apr 29, 2022
@paulfantom
Copy link
Contributor

Related to #288

@paulfantom paulfantom added this to the 0.13.0 milestone Jun 16, 2022
@paulfantom
Copy link
Contributor

We can use up application to test the data flow (cc @onprem)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants