About
Alarm Center
Alarms, the incident log and flight history need the flight-log database, and this server is running without it. Live telemetry on the map is not affected.
Admin settings
When each alarm fires and how loud it is. A change applies to new telemetry straight away and is recorded with who made it.
Escalation
An alarm nobody acknowledges in time is posted to Google Chat, so a second person hears of it outside the browser. It keeps sounding here until acknowledged.
Recent changes
Who acknowledged what, and every change to alarm rules, review limits, the fleet list and access grants. Entries cannot be edited or deleted.
Everyone who has access, by sign-in email, with their role. Adding or removing a user applies at their next request, with no sign-out, and goes in the audit log. Admins add and remove users; only the Super Admin changes a role or adds an Admin.
Add a user
What each role can do
Users
How photos are validated, by the pilot's mission type. Free validates nothing. A photo is judged once, when it is taken.
Services this server calls. Energy OS gives the feeders a power line inspection flies; Flight Radar the manned aircraft near the drones. The token is kept on the server and never shown again; only a super user can change these.
Mission Planner service Not configured
- Link
- No link
- Service
- Not configured
- Last successful call
- never
- Response time
- -
- Errors in the last 24 h
- 0
- Versions
- -
Health
Alarms depend on these. If any stops, every open screen says so.
Services outside this server that it calls. Asked every minute.
The flight database is backed up every night and checked before it is kept. A failed or missing backup turns this amber and is posted to the escalation chat.