...
In the dashboard, each camera has a condition indicator that quickly lets you see if everything with your camera is as it should be:
...
This indicator shows the overall state of the camera. An attempt by the yellow cloud to reduce the available data to something that can give you a quick impression of how your camera is doing.
The indicator is also visible in the camera list, where you can sort and filter for different states in order to get a quick overview over your fleet:
...
Severity
The possible states this indicator can have are as follows:
No Data: The system has received no data from the camera for some time, or ever, and therefore cannot evaluate its condition.
OK: The system has some data, and none of it indicates any problems with the operation.
Warning: There are some errors during operation. Images may still be arriving as scheduled, but all is not well.
Error: The camera is experiencing severe issues that prevent it from sending images. It is still sending data, however.
Critical: The camera unexpectedly stopped sending any kind of data. This most commonly hints at issues with power supply or network connectivity. This condition is only set if there has been no lifesign of the camera for at least three capture intervals.
Active and passive tracking
...
There is no option you have to set to enable active tracking for a camera. Active tracking will kick in automatically as soon as all conditions are met that make it applicable. These conditions are:
A camera needs to be in "operating" status. Any camera that is not marked as operating will not be actively tracked.
A camera needs credentials (a username and a password) defined. If these are not defined, the camera cannot receive any images anyway. Consequently, such cameras are not actively tracked.
A camera needs a schedule defined in the yellow portal. For all yellow webcams, this is always true, as these cameras receive their internal schedule from our servers. If you are using a 3rd party IP-cam, however, we have no way of knowing the schedule with which you have configured them. In this case you need to define the same schedule in the yellow portal to enable active tracking. Active tracking will of course also kick in if the schedules in the camera and the portal do not match, but in this case the evaluation of the cameras condition will be wildly inacurate.
| Anchor | ||||
|---|---|---|---|---|
|
The overall condition indicator is a great way to get a general oversight. But when something is wrong, you may want to know more details about what is wrong exactly and why.
Clicking on an overall condition indicator will take you to that specific cameras condition page, which offers you a much more detailed breakdown:
...
What you see here is the assessment of the camera condition in several separate domains, and the cameras event log.
The event log and events in particular are documented in detail here.
For now, we'll just focus on the condition domains, which are the four cards you see at the top of the window. These are areas of functionality related to the camera, but not all of them relate to the physical camera.
These are the four domains that are separately tracked for a yellow webcam.
Image Upload
Image Processing
Command Channel
Camera Controller
In the case of a 3rd party IP camera, only Image Upload and Image Processing are available, as those cameras won't send any data to our servers.
...
All events have a type, which describes the thing that happened. To read more about specific event types, how to interpret them and the data they carry, please refer to the dedicated events page.
Events that are of severity Warning or Error also carry a message explaining what went wrong.
...
Many events relate to an image. Be that the capturing of an image, the upload of an image, the processing of an image, or even to the fact that the image isn't there. That is, the events refer to a specific image. That also means that a successfully captured, uploaded and processed image leaves a trail of events describing its path. This association between events and a specific image is the event chain, which is identified by the id of the image that created the chain. Each event that forms part of a chain will display that id under the event type if expanded:
...
You can click on this event chain to set the filter to display only events in this chain, making it easier to trace the path of a certain image through the system. You can also enter an image id into the event chain filter field manually, but this is generally not recommended.
...
If you wonder about what certain events mean or how they come about, take a look at our events page.
Combined with the information on this page, you should now have most of the tools to not only easily recognise that something went wrong, but also when, how and why.
...