Flocks allow you to organize Console entities into separate groups. This allows you to create separate Flocks for different teams or locations, splitting access and management between the Flocks.
The following endpoints allow you to perform actions against Flocks on your Consoles, including actions like Creating a new Flock, Deleting a Flock, Moving Sensors to a Flock, and Renaming a Flock.
A Flock allows you to group Sensors and users. It allows you to configure settings that are specific only to the Flock, including notification channels and recipients.
Flocks are defined by a unique flock_id which is returned in the response when calling this endpoint.
Required Parameters
auth_tokenstring
A valid auth token
namestring
The name of the flock
Optional Parameters
managersstring
A comma-separated list of emails who can manage the flock
watchersstring
A comma-separated list of emails who can watch the flock
Deleting a Flock will remove it from your Console. You can only delete an empty FLock, meaning you'll need to move (or remove) any Sensors from the Flock before deleting it.
Move a specified Sensor to a Flock. You'll need to delete all incidents before moving a Sensor between Flocks (this ensures that sensitive data isn't spilled across Flocks). If there are still incidents tied to the Sensor, you can specify clear_incidents=true to clear all of those incidents.
Required Parameters
auth_tokenstring
A valid auth token
dest_flock_idstring
flock_id of the Flock to move to
node_idstring
ID of Bird or Canarytoken to move
Optional Parameters
clear_incidentsboolean
If true, delete all incidents tied to the Sensor before moving it