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

[🐛 Bug]: Info level logs for tracing bloating Node logs #2776

Open
MJB222398 opened this issue Apr 10, 2025 · 3 comments
Open

[🐛 Bug]: Info level logs for tracing bloating Node logs #2776

MJB222398 opened this issue Apr 10, 2025 · 3 comments

Comments

@MJB222398
Copy link

What happened?

I've just gotten round to enabling tracing/telemetry with Jaeger in my Docker Grid. I set it up for the Hub and all the Nodes. If I look at the logs for the Nodes I can see there are lots of 'INFO' level logs relating to the tracing, a seriously large amount bloating the logs. But for the Hub there are no log entries for telemetry. Having a log level of 'INFO' for telemetry seems wrong? And why do they appear for the Node logs but not the hub logs?

Image

Command used to start Selenium Grid with Docker (or Kubernetes)

N/a

Relevant log output

N/A

Operating System

Windows 10

Docker Selenium version (image tag)

4.31.0-20250404

Selenium Grid chart version (chart version)

No response

Copy link

@MJB222398, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

@VietND96
Copy link
Member

Can you copy a full message to see trace events from which operation?

@MJB222398
Copy link
Author

Sure:

09:39:00.927 INFO [SeleniumSpanExporter$1.lambda$export$3] - {"traceId": "4364fab57ddd1505fe0ea450cde8403c","eventTime": 1744364340925536427,"eventName": "HTTP request execution complete","attributes": {"http.flavor": 1,"http.handler_class": "org.openqa.selenium.remote.http.Route$TemplatizedRoute","http.host": "chrome-node-1:5555","http.method": "GET","http.scheme": "HTTP","http.status_code": 200,"http.target": "\u002fstatus","http.user_agent": "curl\u002f8.11.0"}}

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

No branches or pull requests

2 participants