Sites Overview

Sites Basics

A site represents an entity that is monitored by evalink talos. In the real world, this can be a stationary or a mobile object: a building, a car, a mobile surveillance unit, or a single device with a panic button.

A site can receive alarms from a number of sources:

• a connected transmitter

• an integration – for example, an incoming email

• a third party, via a webhook or via evalink talos API

A site can also generate alarms itself: from the schedules, status rules, and workflows configured for it.

info

In the alarm details and in evalink talos UI, a site may sometimes be referred to as a device.

Objects Created for a Site

A site can have the following basic objects created for it:

• workflows that allow to fully or partially automate alarm management scenarios

• a schedule or a number of schedules that can trigger workflows or can be checked by workflows to make decisions

• functional statuses that monitor the state of the site and trigger alarms whenever an unhealthy behavior is discovered

• rules and procedures that allow to handle various external, internal conditions, and combinations of those

• integrations – the connected equipment

Alarms Processing by a Site

After accepting an alarm, a site:

• customizes it, if configured to do so

• logs the resulting alarm

• outputs the resulting alarm: reports or dispatches it to the configured destinations, or sends it for further processing