Has it ever been considered to decouple `status` l...
# general
c
Has it ever been considered to decouple
status
logs from
results
logs when it comes to the logger plugins? In our Kinesis scenario, I want to know when retries get to 0: https://github.com/facebook/osquery/blob/0b62245848992f2d670b794970b31352fbb15121/osquery/logger/plugins/aws_kinesis.cpp#L110-L120, aka we are failing to write to Kinesis and dropping logs. However, I can't do that unless I configure the filesystem logger or some other logger plugin, but then I'm sending both status and results logs to that too, a performance hit I can't accept when I just want to send the status log to somewhere to know that my Kinesis pipeline is having issues. This type of problem impacts anyone that's doing remote logging. I'm surprised no one else has experienced this issue?