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

(suggestion) venom logs formatting and content #790

Open
mxm-tr opened this issue Apr 25, 2024 · 0 comments
Open

(suggestion) venom logs formatting and content #790

mxm-tr opened this issue Apr 25, 2024 · 0 comments

Comments

@mxm-tr
Copy link

mxm-tr commented Apr 25, 2024

The new logs format that was introduced after venom 1.0.0 can be sometimes difficult to read/parse and does not contain that much information. It could be helpful to have more details sometimes for debugging failing tests.

Apr 18 16:36:54.602 [ERRO] [Cluster creation] [CreateService] Errors: 
Apr 18 16:36:54.602 [ERRO] [Cluster creation] [CreateService] Testcase "CreateService", step #0-0: Assertion "result.statuscode            ShouldEqual 200" failed. expected: 200  got: 401 (cluster_creation.yaml:0)

In previous versions, the key value format was much easier to parse for example

time="2024-04-11T19:13:25+02:00" level=debug msg="teststep exec '/bin/sh /tmp/venom-249556880'" v.testsuite="Create Service [kubernetes/cluster_creation.yaml]" x.testcase=CreateService 

Would it be possible to:

  • Pick a different location for logs (stdout, or a file)?
  • More logs formatting options (json) ?
  • More information displayed in the debug logs (http client headers and payloads, execution times and more)?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant