node-red / node-red/node-red-nodes
Excessive logging with ping
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
I use node-red to monitor the availability of my IoT / other devices by pinging them every 20seconds. Although this is probably not the ideal method it works for me but unfortunately it generates excessive amount of log messages like this.
15 Jun 15:35:21 - [info] [ping:5c31503383df695d-1683c145933c6c70] ping - Host '192.168.x.x' process timeout - sending SIGINT
I would like to make an argument that this should not be a info-level message, but rather debug.
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 tracing the ping node's timeout path that emits the reported process-timeout message. Confirm where its log level is selected and verify that this timeout is no longer emitted at info level; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100