Debug log messages marked as info
level #160
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#160
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Expected Behavior
Debug log messages should be marked as
debug
levelCurrent Behavior
Debug log messages marked as
info
levelSteps to Reproduce (for bugs)
2.Try to create container
info
levelVersion
Your Environment
HW
4 nodes
Debug log messages should be marked asto Debug log messages marked asdebug
levelinfo
levelThose logs were intentionally set with INFO level. The idea was to have at least some records for every processed requests. This is especially important when gateway hidden besides nginx proxy and we might not be sure whether request is even come to the gateway.
Do you think this is too verbose? Maybe we can keep at least
start
messages in the logs./cc @anikeev-yadro
No this is not too verbose. I suggest to keep this. You can close the issue.