hi all, anyone using osquery module in filebeat wi...
# general
k
hi all, anyone using osquery module in filebeat with ELK. all my fields in kibana starts with json. i.e json.host_identifier despite having var.namespace: true
d
var.use_namespace should be true by default. I have not set it, and I am seeing expected results (ie osquery.result)
k
@defensivedepth not for me, a lot of items are starting as json.host_Identifier, etc
d
What does your osquery module config look like? Also what version are you running?
k
@defensivedepth filbeat version 6.3.2
filebeat.modules: - module: osquery result: enabled: true var.paths: [“/tmp/osquery_result”] var.use_namespace: true
d
hmmm. Are you doing any processing in Filebeat before outputting? Also, what does your FB output look like?
k
i dont think so, the FB output from /logs u mean ?
that looks normal
d
Under your FB Outputs, are you sending directly to ES?
k
logstash
should it be to ES instead?
d
Well, that is probably the issue. iirc, the osquery module uses the ES ingest node, so that is probably where some of that of that normalization is happening.
k
so, send the data from filebeat to ES and then ES will deal with the rest ?
let me try
d
Yes, try that
k
nope gave me an error
that connection refused but i know 9200 is open and listening
its from one box to another
d
Can you do a successful ‘curl ElasticHost:9200’ from the FB system?
k
nope connection refused
but on the elk box same this does output
so i think it just not listening outside of itself
d
Check the ES config file (elasticsearch.yml) for the network.host setting. https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html
k
yup that was it
it wasn’t set to accept outside of 127.0.0.1
am getting a kibana error but let me check
d
not sure of your setup, but make sure that it isnt publicly accessible now 🙂
k
yeah
it now works
thanks the issue was i wasn’t sending to elasticsearch and directly to logstash @defensivedepth thank you
🍻 1