Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

#14916 Configuration change: Host status webhook per-team (#15612)

Browse Source 
Adds `webhook_settings.host_status_webhook` options to team config for
#14916.

Also updated conceptual docs that reference this config (and cut down
some content to make room).
This commit is contained in:
Rachael Shaw
2024-04-10 15:28:17 -05:00
committed by GitHub
parent 63ca8f44be
commit 57a28ed18d
3 changed files with 17 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/Using Fleet/Automations.md
+6 -4
View File
@@ -130,9 +130,9 @@ Follow the steps below to configure Jira or Zendesk as a ticket destination:
## Host status automations
Host status automations send a webhook request if a configured percentage of hosts have not checked in to Fleet for a configured number of days.
Host status automations send a webhook request if a configured percentage of hosts have not checked in to Fleet for a configured number of days. This can be customized [globally](https://fleetdm.com/docs/configuration/configuration-files#organization-settingss) or [per-team](https://fleetdm.com/docs/configuration/configuration-files#teams).
Fleet sends these webhook requests once per day by default. This interval can be updated with the `webhook_settings.interval` configuration option using the [`config` YAML document](https://fleetdm.com/docs/using-fleet/configuration-files#organization-settings) and the `fleetctl apply` command. Note that this interval currently configures both host status and failing policy automations.
Fleet sends these webhook requests once per day by default. This interval can be updated with the `webhook_settings.interval` [configuration option](https://fleetdm.com/docs/configuration/configuration-files#organization-settings). Note that this interval currently configures both host status and failing policy automations.
Example webhook payload:
@@ -147,9 +147,11 @@ POST https://server.com/example
because the Host status webhook is enabeld in your Fleet
instance.",
"data": {
"unseen_hosts": 1,
"total_hosts": 2,
"unseen_hosts": 3,
"total_hosts": 12,
"days_unseen": 3,
"team_id": 123,
"host_ids": [1, 2, 3]
}
}
```