...
There’s only two parameters to adjust here:
Monitoring domain: The domain the alarm should listen to. Those are either Upload, Processing, Command or Controller.
Raise alarm on states: The states the chosen domain has to be in for the alarm to be raised. Note that the Critical state is available only for the Overall domain.
The alarm will be raised if the condition of the configured domain is in any of the configured states.
A few helpful further tips:
The overall domain is a general summary of a cameras overall functionality. It will be Error if the camera is unable to receive images. It is the only domain that can have the “Critical” state, which means that a camera has dropped of the net completely.
Only cameras with the webcam-controller peripheral support the command and controller domains. Listening to these domains on an IP-camera sending by FTP will have absolutely no effect.
Actions
Actions determine what happens when an alarm is raised for a camera. Certain actions have the added benefit of allowing extending their configuration on a per-camera basis, without altering the base configuration of the alarm. This means that these actions can also be extended by power users, so that some of your end customers can influence additional behavior. This is especially important for notifications, where customers can add additional email addresses to receive alarm notifications for their cameras themselves, and define custom messages specifically tailored to the camera and alarm.
...