IoT administration
How your nominated administrators configure the office monitoring service: where sensors are, how they connect, what they test and who is told when something goes wrong.
The admin area is being consolidated in the next release. This guide describes each task by what you set and why, not by screen layout. The order of the steps and the settings themselves stay the same.
Before you start
The administration views are restricted to the senior staff you nominate. Everything is set in the portal, not on the devices.
The order to work in
- Sites: the offices being monitored.
- Sensors and network profiles: which sensor is where, and how it connects.
- Wireless maps: where each sensor sits on each floor.
- Applications: what the sensors test.
- Alerts: who is told, and when.
How changes work
- Select the item to change, such as a site, sensor or application, and edit it in its form. Changed values are highlighted, and the submit button becomes active.
- Submit, then confirm the change when asked.
- Every sensor picks up the change within a poll cycle. Alert rules regenerate automatically.
Every change is recorded in an audit trail: who changed what and when, with the old and new values. The trail is kept for a year.
Standard allowances
| Item | Included |
|---|---|
| Sites | 12 |
| Applications | 12 |
| Network profiles | 25 |
| Wi-Fi networks | 25 |
| Ethernet networks | 25 |
| Email notification groups | 6 |
Each can be raised on request: contact support.
Sites
A site is one office. The portal comes with a fixed set of site slots; select one and fill it in.
| Setting | What it does |
|---|---|
| Site code | A short code you choose to identify the site. The portal uses it to group the data from the site's sensors. No spaces or special characters. |
| Address | Shown in the title of the site's views. |
| Number of sensors | The sensors deployed at the site, shown on the site's views. |
| Status | Enable or disable the site. A disabled site disappears from the views and can't be chosen for a sensor. |
| WAN 1 public IP | The public IP address of the office's internet or WAN connection, probed from the cloud. |
| WAN 1 probe | Ping by default. If the circuit doesn't answer ping, choose trace instead. |
| WAN 2 public IP and probe | The same for a second circuit, if the office has a resilient connection. |
Some fields lock. The site code, status and WAN settings can't be changed while the site has wireless maps or WAN alerts. To change them, delete the site's wireless maps and disable its WAN alerts first, then recreate them.
Sensors
Each sensor is identified by the Device ID printed on the label at its back. Select the Device ID, then set:
| Setting | What it does |
|---|---|
| Site | The site code the sensor belongs to. |
| Floor | The floor it is on. Together with the site and number, this forms the name the sensor has in the portal. |
| Sensor number | Distinguishes sensors on the same floor. |
| Positioning notes | Free text, for example the desk or room. Useful when someone needs to find the sensor. |
| Status | Enable or disable the sensor. A disabled sensor disappears from the views. |
Then assign the sensor a network profile, which tells it how to connect.
Network profiles
A network profile tells sensors how to join your networks. Each profile holds up to 3 Wi-Fi networks and 1 Ethernet network, and a sensor assigned to the profile can use any of them. Assign a profile to one or more sensors.
- Failover: include both your normal network and your disaster-recovery SSID, and give the disaster-recovery SSID the higher priority so sensors prefer it whenever it is broadcast.
- Several offices, one profile: if three offices each have their own SSID, put all three in one profile. Sensors using it can then work in any of the three offices.
ModelA sensors are wireless only, so only the Wi-Fi networks in a profile apply to them.
Wi-Fi network settings
| Setting | Options |
|---|---|
| SSID | The network name. |
| IP allocation | DHCP, or static with IP address, subnet mask, default gateway and two DNS servers. |
| Priority | Which network a sensor tries first when several are available. Higher is preferred. |
| Authentication |
|
Ethernet network settings
IP allocation by DHCP, or static with IP address, subnet mask, default gateway and two DNS servers.
Wireless maps
A wireless map is the floor plan behind a floor's Wi-Fi view. You need the floor plan as an image and a record of where each sensor was installed.
- Generate a draft. Choose the site and floor and upload your floor plan image. After about a minute the portal produces a draft map with numbered sensor icons on your plan. Download it.
- Position the sensors. Open the draft in the diagram editor provided in the portal. Move an icon to each real sensor's position, name it to match the sensor, and delete the icons you don't need. Save the file to your computer.
- Publish. Choose the same site and floor, upload the saved file and submit. The floor's Wi-Fi view is created and appears in the site's list of wireless views.
Update or delete an existing map from the same place.
Applications
The applications every sensor tests, every two minutes. For each one, set:
- Name: how it appears in the views.
- URL: the address the sensors test.
- Status: enable or disable testing. A disabled application also disappears from the views.
Results appear in the application views and on each site's view. If you replace one application with another, the old one's history is kept: for a time range that spans the change, you'll see both.
Alerts
You set the thresholds and recipients in simple forms; the alert rules build themselves. A sustained problem typically raises an alert in about 10–15 minutes, an estimate based on the default settings: rules are checked every two minutes and must stay in breach for ten.
Email groups
Alerts go to email notification groups. For each group set:
- the recipients' email addresses
- whether to send one combined email to everyone or one per recipient
- whether the group is also told when an alert is resolved
- whether the group is enabled. Only enabled groups can be chosen for an alert.
Alerts to Teams, Slack, ITSM or on-call tools can be set up on request.
Alert types
| Alert | Set per | Threshold | Notes |
|---|---|---|---|
| Application | Application | Response time | Enable or disable, set the threshold and choose the email group. |
| Per-site application | Site | Seconds, on the combined response of up to 3 applications | Fires on the aggregate, so one application wobbling doesn't alert while the others are fine. Choose applications with similar response times. |
| DNS | Site | Milliseconds | Lookup time against the DNS server configured for, or given by DHCP to, the sensors. |
| WAN latency | Circuit (WAN 1, WAN 2) | Latency, per circuit | Available once the site's WAN IP is set. Packet loss is fixed at 10%. |
| Wi-Fi signal | Site and floor | dBm | Fires when signal on that floor falls below the level you set. |
| Sensor offline | One or more sensors | None | Offline sensors are grouped into one alert. |
Every alert can be enabled or disabled, and sends to the email group you choose.
What the alerts measure and how they are evaluated: Data and alerting.