Support the vmodule command line flag

[Patagonia121]

• customer-figali Slack thread: https://fleetdm.slack.com/archives/C06GSN6HR6D/p1736987491691839
• @noahtalerman: User requested this because they want to enable verbose logging for specific osquery errors so that they can limit the amount of noise while debugging osquery issues. Today, when they try to add this flag in the UI (Organization settings > Agent options), they see an error that says "this flag isn't supported"
  • @noahtalerman: In the interim the user can force apply the agent options with the fleetctl apply -f agent-options.yml --force. This will bypass Fleet's validation.
  • @noahtalerman: Eventually Fleet could add vmodule as a supported flag.

User stories

• Agent options: allow vmodule command line flag #25838

[Patagonia121]

@noahtalerman the customer feels this is a minor change/addition to the product and doesn't want to wait a month to go through this on a call, so I'm bringing forward now and have included the Slack thread where the discussion originated from. Thanks!

[noahtalerman]

Hey @sharon-fdm can you please help us confirm that the --vmodule command line flag works on the latest osquery version?

Fleet errors if you try to set this in Agent options today. See the customer Slack thread for more info here: https://fleetdm.slack.com/archives/C06GSN6HR6D/p1736987491691839

[sharon-fdm]

@noahtalerman, we have some BW to take this into our board if you'd like. It shouldn't be a big thing.

[noahtalerman]

@Patagonia121 heads up, we peeled a user story (#25838) off of this request and prioritized it (brought it onto the drafting board).