Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

Hey everyone!

I'm setting up a new environment to test some new things, but I'm *having difficulty* using the webhook options.

The idea is to output everything to the webhook.

```mysql:
  address: 127.0.0.1:3306
  database: 'fleetdm'
  username: 'fleetdm'
  password: '123'
redis:
  address: 127.0.0.1:6379
server:
  address: 127.0.0.1:8080
  tls: false
auth:
  jwt_key: 'XXXXXXXXXXXX'
filesystem:
  status_log_file: /var/log/osquery/status.log
  result_log_file: /var/log/osquery/result.log
  enable_log_rotation: true
logging:
  json: true
osquery:
  result_log_plugin: 'webhook'
webhook:
  result_url: '<http://127.0.0.1:9880>'```

Hi <@U08RS3N1D4K>! What version of Fleet are you running? Can you tell me a bit more about the logging destination you're trying to test?

Version: fleet_v4.68.0_linux

The log destination I'm trying to test is a webhook. My ultimate goal is to integrate Fleet with *fluent-bit*, so that Fleet sends events to a webhook endpoint that will be received by fluent-bit. From there, fluent-bit will handle the processing and forwarding to my testing logging system.

Could you try updating to 4.69? Additionally, I'm curious if there's some internal firewall issue on your system that could be blocking the incoming webhook.

I fixed it :slightly_smiling_face:

Was missing the automations enabled on the schedule queries!

Thx anyway!