Events describe things that happened in relation to your images or cameras at a specific point in time. All events have the following common characteristics:

An event type: The nature of the event, and by extension of the operation that spawned it. A complete list and explanation of the various event types is below.
A severity of either OK, Warning, or Error. Ok means that an operation succeeded as expected, warning means that while it succeeded, some things didn't quite go as they should, and error means that whatever the event describes failed.
A time: This is the time the event was generated at, which in some cases may not be the same time the operation it is refering to actually happened. A MissingHeartbeatEvent, for example, will be generated some minutes after the heartbeat of a camera stopped.
A Message: In the case of events of severity OK, the message is usually omitted, but warnings and errors will always carry a message to explain what went wrong.
Additional data: By clicking on the severity indicator of any event, you can expand it to see additional data, which varries by event type. Some event types have only very little additional data, while others have quite a bit. This data is intended to provide you with more of an oversight on how things were at the time the event was generated.

Event types

This is a conclusive list of all event types that can occur, explaining what they mean and the data they carry.

ImageCaptureEvent

domain	Camera Controller
meaning	The camera attempted to capture an image.
severities	OK: The capture succeeded and the image went on to be uploaded. Warning: The capture succeeded and the image went on to be uploaded, but not the entire configuration for the camera could be set. Error: The image could not be captured, usually due to some error involving the attached camera itself.
data	The camera configuration the image was supposed to be captured with.
applies for	Only Yellow Webcams

CameraOperationEvent

domain	Camera Controller
meaning	A catch-all event for various operations of the camera controller like startup and shutdown, focusing or starting the heater.
severities	OK: The operation in question succeeded. Error: The operation in question failed.
data	The exact operation the event refers to.
applies for	Only Yellow Webcams

ImageUploadEvent

domain	Image Upload
meaning	A camera of any type uploaded an image to the yellow gateway, or a yellow webcam uploaded an image to a 3rd party server.
severities	OK: The image was successfully uploaded. If it was uploaded to the yellow gateway, this means that it will shortly continue to image processing. In case of an upload to a 3rd party server, this event concludes the event chain. Note that a successful upload via FTP does not necessarily mean that the upload was complete. It is notoriously difficult to tell whether an ftp client has uploaded the whole file or only parts of it. Error: The image upload failed to commence or to complete. Yellow webcams may attempt a re-upload at a later time, typically at the next reboot. This will produce further UploadEvents in the same event chain. Uploads to 3rd party servers are not retried.
data	The endpoint of the upload.
applies for	All cameras

PanoramaUploadCompleteEvent

domain	Image Upload
meaning	All images belonging to a panorama images have been uploaded
severities	OK: All component images were successfully uploaded and are forwarded to be stitched Error: One or several component images of a panorama had errors in its event chain and is missing. The panorama cannot be stitched.
data	How many component images the panorama consists of.
applies for	Only panorama cameras

ImageProcessingEvent

domain	Image Processing
meaning	The processing configuration of one table has been applied to the image, and the image was stored successfully. Consequently, there should always be one ImageProcessingEvent per table per image.
severities	OK: The configuration could be applied without issues and the image was stored. Warning: The configuration could be applied and the image stored, but there were some irregularities. This is most often the case if you configured a redirect to a 3rd party server, and the upload to that server failed. Error: The image configuration could not be applied and the image was not stored. This does not mean that the image is entirely lost. Another attempt at processing the image will be made in a few minutes, to a maximum of 3 attempts that will generate further ImageProcessingEvents in the same event chain. If the reason for a failed image is a faulty configuration, however (cropping outside the image borders is a favorite), these subsequent attempts are doomed to fail unless you fix the processing configuration in question.
data	The name of the table the image was processed for, as well as the complete processing configuration for that table at the time the image was processed.
applies for	All cameras

PanoramaStitchingEvent

domain	Image Processing
meaning	The stitcher has finished stitching a panorama image, whether successfully or not.
severities	OK: The image has been stitched and forwarded for any further processing you may have configured. Error: The image could not be stitched. Another attempt at stitching the image will be made in 15 minutes, to a maximum of 3 attempts, that will generate further PanoramaStitchingEvents in the same event chain.
data	Access to the component images the panorama consists of. The output of the stitching operation itself, giving you potential pointers to what exactly went wrong and what you might have to fix to make the panorama work.
applies for	Panorama cameras

MissingHeartbeatEvent

domain	Command Channel
meaning	A Yellow Webcam sends a heartbeat every minute to keep the system apprised of its overall status. This event type signifies that this heartbeat has stopped during the last couple of minutes, or that it has returned after having stopped for some time.
severities	OK: The heartbeat of the camera was missing, but has now returned. Error: The heartbeat has been absent for a couple of minutes. The camera will currently not be able to receive settings or commands, though it may still be sending images. If the situation endures, this event is regenerated every hour.
data	The exact time the last heartbeat was received, in UTC.
applies for	Only Yellow Webcams

MissingImageEvent

domain	General
meaning	An image that should have been received according to the cameras schedule did not arrive.
severities	Error: What it says on the tin. If there is any indication of the image in the event log (like failed uploads or capture), this event will be linked to the same chain. But if neither the image nor any related events are present, this event will not have an event chain. MissingImageEvents are generated for every image that should be there, but isn't.
data	The schedule of the camera as it was at the time the event was generated, the exact time when the image should have been captured according to that schedule, as well as the time the last image by this camera was successfully submitted and processed.
applies for	Any actively tracked cameras.

CameraMIAEvent

domain	General
meaning	A camera is "missing in action". In other words, the system knows it was working, but now seems completely absent. The cause for this is most frequently a severed network or power connection.
severities	OK: The camera was missing, but has now resumed communication. Error: The camera stopped communicating for at least 3 full image intervals according to its schedule. For 3rd-party cameras, this simply means that there have been no uploads. For a yellow webcam, it means there have been no uploads, no heartbeats, and no events from the camera. A CameraMIA error is therefore usually preceded by 3 MissingImageEvents and no other events at all. If the situation endures, this event is regenerated every hour.
data	The time the last lifesign of the camera was received.
applies for	Any actively tracked cameras.

Browser not supported