Open c-kruse opened 1 week ago
@ajssmith wanted to get your take on this approach before cleaning it up a bit. I'm still on the fence about the "flow-logging-profile" flag.
Background: In skupper v1 the volume of logs coming from a collector handling a lot of vanflow records could be a problem. In v2 I dropped flow logging to avoid the issue. For the most part I have not missed them - I have been leaning more on some of the new internal metrics the collector publishes, but there's been a time or two I wish I had them.
Starting out on the problem, I went with a fully user configurable per-record-type-regex-matching sampling but found that was too much to configure as a user. I've since moved to offering "profiles" with different sampling strategies set at somewhat arbitrary levels. Thoughts on this approach? Other suggestions?
EDIT Went forward with cleaning out some of the original cruft. Considering this fully ready for review!
flow-logging-profile
flag to allow opt-in for the logging of vanflow records with some coarse control over the volume of log events though sampling.