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

osquery

Quick question. I'm testing new fleetdm 3.8 thats seems great. Just in case I was playing with some config options and I tried to change `config_refresh:10` to 60 as other fields I changed but looking into new drilldown it seems like nothing changed. Is it possible to change config_refresh using fleetctl ?

image.png

I didn't test this config_refresh test in previous version.

Logging at osquery_flags seems like there config_refresh with my new parameter.

The host details page will take some time to update (configurable via <https://github.com/fleetdm/fleet/blob/master/docs/2-Deployment/2-Configuration.md#osquery_detail_update_interval>).

By default it's an hour, so it could take a little while to see the correct value there.

but other too values changed in minutes hehehe but I will that to see :smiley: Thanks!

Can you run osquery with `--verbose --tls_dump` and see if it receives the expected value from Fleet?

seems like receiving, just applied new options

```I0225 16:44:25.828430 314369 smbios_tables.cpp:105] Reading SMBIOS from sysfs DMI node
I0225 16:44:25.828779 314369 config.cpp:890] Calling configure for logger tls
I0225 16:44:40.829082 314369 config.cpp:1205] Refreshing configuration state
I0225 16:44:40.829715 314369 tls.cpp:254] TLS/HTTPS POST request to URI: <https://localhost:8412/api/v1/osquery/config>

{
  "decorators": {
    "load": [
      "SELECT uuid AS host_uuid FROM system_info;",
      "SELECT hostname AS hostname FROM system_info;"
    ]
  },
  "options": {
    "config_refresh": 17,
    "disable_distributed": false,
    "distributed_interval": 37,
    "distributed_plugin": "tls",
    "distributed_tls_max_attempts": 3,
    "logger_plugin": "tls",
    "logger_tls_endpoint": "/api/v1/osquery/log",
    "logger_tls_period": 47,
    "pack_delimiter": "/"
  }
}```

Okay cool, let's see if it updates properly after waiting.

Not sure when it changed, but changed heheheh

but other two changed almost in real time

That is interesting that it eventually worked. I opened up an issue to investigate further since  other users had similar issues. <https://github.com/fleetdm/fleet/issues/357|https://github.com/fleetdm/fleet/issues/357>