-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collector logging #1828
Collector logging #1828
Conversation
Example network-observer startup logs with |
Signed-off-by: Christian Kruse <[email protected]>
Implements several "profiles" to control the quantity of vanflow record logging the collector does. Defaults to silent. Primairly a debugging aid. Signed-off-by: Christian Kruse <[email protected]>
Convert record map into slog.Group Signed-off-by: Christian Kruse <[email protected]>
f42685e
to
58271df
Compare
cmd/network-observer/profiles.go
Outdated
Match: flowlog.NewRecordTypeSet( | ||
vanflow.SiteRecord{}, vanflow.RouterRecord{}, | ||
vanflow.ProcessRecord{}, vanflow.ConnectorRecord{}, | ||
vanflow.LinkRecord{}, vanflow.ListenerRecord{}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should LinkRecord be part of both rules (priority 5 and 1)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, there was no real sense in that. Dropped it from the p 5 rule (lowest wins). Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Played a bit with the different strategies and they seem to work well.
Signed-off-by: Christian Kruse <[email protected]>
Reopens #1783
I believe we've sorted out that this sort of a protocol-level vanflow logging option is useful for debugging different scenarios, but is not a particularly nice solution for users looking for an audit trail for service traffic. I've opened #1827 to tackle that use case.