You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Kerberos Agent supports a remote recording trigger through an HTTP API call:/api/motion. When hitting the API endpoint, the Kerberos Agent will initiate a new recording. This is a great solution for "time based" analysis or documentation; for example following up the progress of a construction area, evolution of process (plants, fish, etc).
With this feature, we would like to scale up this feature, where you can leverage Kerberos Factory to trigger motion on all its Kerberos Agents. This would simplify the process and make it easier to manage when scaling out more cameras, and still have the ability to have single API endpoint which orchestrates.
Outcome:
New Kerberos Factory HTTP method
POST api/recordq
The text was updated successfully, but these errors were encountered:
Currently the Kerberos Agent supports a remote recording trigger through an HTTP API call:
/api/motion
. When hitting the API endpoint, the Kerberos Agent will initiate a new recording. This is a great solution for "time based" analysis or documentation; for example following up the progress of a construction area, evolution of process (plants, fish, etc).With this feature, we would like to scale up this feature, where you can leverage Kerberos Factory to trigger motion on all its Kerberos Agents. This would simplify the process and make it easier to manage when scaling out more cameras, and still have the ability to have single API endpoint which orchestrates.
Outcome:
New Kerberos Factory HTTP method
POST
api/record
qThe text was updated successfully, but these errors were encountered: