codenotary / codenotary/immugw
The Immugw logs are not available
- Dominant language
- Go
- Stars
- 27
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
The current log file of immugw shows the content like this
immugw 2023/11/29 07:06:27 INFO: starting immugw: {"Dir":".","Address":"0.0.0.0","Port":3323,"MetricsPort":9476,"ImmudbAddress":"127.0.0.1","ImmudbPort":3322,"Audit":f>immugw 2023/11/29 07:06:27 ERROR: unable to launch immugw: listen tcp 0.0.0.0:3323: bind: address already in use
The logs never get generated for
1. incoming requests from my Node.js services
2. the outgoing request from immugw to immudb
Without the logs it is really difficult to trace out the issues in immugw.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the immugw entry points that handle incoming requests and outgoing calls to immudb, then inspect how logging is configured for those paths. Reproduce a request from a Node.js service and confirm that both request directions produce usable log entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, node.js
- Domain
- api, backend, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100