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

[Feature] redesign observability tracing test #2108

Open
kosstennbl opened this issue Jul 15, 2024 · 0 comments
Open

[Feature] redesign observability tracing test #2108

kosstennbl opened this issue Jul 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@kosstennbl
Copy link
Collaborator

Currently, for tracing test, we have code that checks if tracing is used as a part of CNF installation, and writes info about it to the config. During the test - config is read and result is given based on written info.

Problem is that adding complexity to the CNF setup process is not ideal (#2036), and from my point of view - we should find another way to check if Jaeger tracing is enabled in CNF.

Also, the tests seems a bit too specific as it is tied to using Jaeger. Maybe some other way could be found.

@kosstennbl kosstennbl added the enhancement New feature or request label Jul 15, 2024
@kosstennbl kosstennbl changed the title [Feature] redesign observability tracing test. [Feature] redesign observability tracing test Jul 16, 2024
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

No branches or pull requests

1 participant