full logging is very verbose.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.8k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 41
Description
Feign logging FULL is very verbose, up to 16 log messages per REST call (depending on headers). Is there any chance of an option to produce just two log messages in JSON format? Example for reply:
{
"status": 200,
"response_headers": [<list of HTTP response headers>],
"payload": <REST payload>
}
Everything in a single log message. This would provide the same really useful information but in a format that would greatly reduce the load on log aggregators such as ELK.
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 Feign's FULL logging entry point and any existing logging tests; the issue does not name specific files. Define how the option would consolidate a REST call into JSON log messages, and consider the request and response information that must remain available. Done means the new option reduces message volume while retaining the useful information described in the example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100