Daily briefing
Overview > Daily briefing gives the people who run the fleet one short read a day: the state of the fleet, what is new, and the actions that matter most today. It is sent to the email addresses and the Slack or Teams webhook under Settings, and the latest one is always on the page.
What is in it
Gardience works out the facts itself, from its own data:
- machines patched and passing the baseline, updates waiting, machines waiting for a reboot, machines not answering
- CVEs new on your fleet (see Vulnerabilities), and the fixable CVEs on the most machines
- runs that failed in the last day, and runs waiting for approval
- machines with configuration drift
It then builds the recommended actions, also itself, as exact requests the console already checks: Fix a CVE on only its exposed machines, Patch a node group on the pilot ring, or a page to look at (approvals waiting, failed runs, machines not answering, drift).
With the AI assistant on, your model writes a short summary and picks the three actions that matter most from that list, with a reason for each. It cannot add an action of its own; a pick that is not on the list is dropped. It is sent only the facts shown on the page. Without the assistant, or if the model does not answer, the briefing goes out in plain wording with the first three actions.
Acting on it
Each action has Run (or Open for a page). Run starts the request as you, and it then goes through your permissions, change windows, locks and approvals like any run. Nothing runs from the briefing by itself.
Turn it on
An admin ticks Send daily under Overview > Daily briefing > Settings and picks the hour (UTC; 12 is 7 AM US Central). Write one now writes one at once without sending it. Each briefing is recorded in the audit log (briefing.sent), with the model that wrote it and the actions it recommended. The last 30 are kept.