Amit Shani
08/26/2025, 1:22 PM--config_plugin=mycustomconfig I’ll get an error saying this plugin is unknown.
The example I know to work with config plugin work the opposite way:
./osqueryd --extension /path/to/config.ext --config_plugin=mycustomconfig
but in this case osqueryd needs to spawn the extension binary.
Is there any approach in which I can run osqueryd and register myself as config plugin without making it spawn a different process?Stefano Bonicatti
08/26/2025, 4:56 PM--extensions_require=mycustomconfig to have osquery wait indefinitely for that plugin to register itself.Stefano Bonicatti
08/26/2025, 4:57 PMseph
seph
--extension argument has osquery spawn the extension binary with the expected arguments. To invert that, you need to make sure osquery is listening on the the socket path you expect, and have your thing go and use it.
Options like config_plugin tell osquery to use the extension that registered with that name for the config. But do nothing to actually start the extension.
You'l want extensions_require so that osquery pauses it's startup waiting for those extensions to registerAmit Shani
08/27/2025, 7:33 AMAmit Shani
08/27/2025, 8:11 AM