SeleniumHQ / SeleniumHQ/docker-selenium
[🐛 Bug]: Info level logs for tracing bloating Node logs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
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?
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Docker Selenium 4.31.0-20250404 setup with Jaeger tracing enabled for both the Hub and Nodes, then compare their telemetry-related logs. Determine why Node logs contain many INFO entries while Hub logs do not, and document or correct the expected logging behavior with evidence from the reproduced logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100