-
Notifications
You must be signed in to change notification settings - Fork 195
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
log-level behaviour #120
Comments
@dili91 ok, it's still not clear what is the problem. Log is very detailed and shows every |
Hello, basically I was expecting to see traffic logs with log level set to debug but I might have misunderstood. I'd like to check those because latency applied to the targeted container is not inline with the netem delay I set. I guess due to some unexpected internal loop, which I wanted to troubleshoot. Is there a way I can do it ? Thank you |
@dili91 take a look at code and if you see any unexpected delay suggest a PR. You can also try to run |
I'm experiencing some unexpected behaviour when netem delay command is applied on one of my docker container. In order to troubleshoot this I tried to use the --log-level option with debug level. With this option i was just able to see the initial execution plan and not the commands executed while running the test. What am I missing ? I also tried with --tc-image gaiadocker/iproute2 but I can see the same output (except for iproute2 container creation) that is :
The text was updated successfully, but these errors were encountered: