logger: Add journald support #971
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#971
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-node:feat/zapjournald"
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?
Relates #736
Now it is possible to specify
journald
destination for logger.The same approach as
c334adeb6d/cmd/s3-gw/app_settings.go
Now
journalctl
uses zap's level:Signed-off-by: Dmitrii Stepanov d.stepanov@yadro.com
@ -1012,1 +1014,4 @@
}
err = c.dynamicConfiguration.logger.SetDestination(c.LoggerCfg.destination)
if err != nil {
// not expected since validation should be performed before
Where is validation performed?
I see a comment in the previous
if
but it could be misleading too.Also, do we change this on SIGHUP? Not saying that we need to (it could be even harmful), just to know
Here:
cmd/frostfs-node/validate.go
No.
@ -38,2 +43,4 @@
}
const (
DestinationUndefined = ""
We also have
Loki
which doesn't use this field. What about unifying the approach? (destination: loki
)loki
works with both ofjournald
andstdout
, it is not a destination.Journald core can work with stdout too (it does by default I think)
So then
destination
possible values will bestdout
,journald
,stdout+loki
,journald+loki
? Looks ... strange.