`--logger_plugin=something_other_than_filesystem`
# kolide
g
--logger_plugin=something_other_than_filesystem
r
for my logger pluggin i have --logger_plugin=filesystem
nothing shows up in ProgramData\osquery\log
i also added --osquery_status_log_file:\ProgramData\osquery\log
nothing works…all this on a windows end point
yes the daemon connects to kolide very easy.. so it cant be the flag file
g
can you run it with --tls_dump and see that your packs are being schedule?
r
im using kolide
g
i dont care what you’re using on the other end. I’m asking about running osquery in your shell and adding the --tls_dump flag so you can debug it
r
did that already
not working
g
what is not working
what are you seeing in tls_dump
r
why is the logger pluggin tls
Here is the flag file