InnerWeb
Skip to main content

Checklist: host version consistency after deployment

After an update every host must have the device log endpoint, and every watch must run the app in the same version. A host without the endpoint returns 404 and stays blind, even though the map works. The checklist guides the rollout team through checking the hosts, the versions and a final test.

404
host response without the log endpoint
Source: karta
78 s
log sending interval at a 26 s heartbeat interval
Source: karta

Why version consistency must be checked after deployment

After a system update the rollout team must confirm two things: that every host has the endpoint that saves the device log, and that the app on the watches is in the same version as the backend. The log saving function works only on hosts where the backend with this endpoint has been deployed. A host that has not been updated returns 404 and stays blind: the watches send batches, and the server does not accept them.

This state is not visible on the map or in the employee positions, because the heartbeat works independently of the log. For this reason, without a deliberate check, the mismatch can go unnoticed until the first incident in which event records are missing.

Step 1: checking the log endpoint on every host

For every host in the rollout network, make a test call to the log endpoint with a test device or a test account. The expected response is a confirmation that the batch has been accepted. A 404 response means that the host does not have the backend with this function deployed. A 400 response means that the host knows the endpoint but rejects the batch because of an invalid entry: the server rejects the whole batch with code 400 when even one entry is invalid.

Record the result in a table: host, response, date and person. In a sample network of five hosts, a result of 4 correct out of 5 means that one host requires immediate repair. The example is illustrative and does not describe a specific installation.

Sample check of 5 hosts

Sample check of 5 hostsDonut chart: 4 hosts respond correctly, 1 returns 404.Responds correctly: 4 hosts (80%)Returns 404: 1 hosts (20%)5hostsResponds correctly4 hosts (80%)Returns 4041 hosts (20%)
Source: Sample calculation: illustrative network of five hosts, not a specific installation

Step 2: the app version on the devices

The app version is often recorded in several places and may diverge. The version from the package manifest, reported by the device management system, is taken as the truth. Do not base the check on the number shown in the settings or in the deployment description if it differs from the report of the management system.

Export from the device management system the list of watches with their version and compare it with the target version. Devices on an older version must be updated, and those that do not report must be checked physically. Record the number of compliant and non-compliant devices.

Step 3: verifying the effect, that is the log from the device

After checking the hosts and the versions, carry out a final test. Trigger a test event on the watch and wait for the batch to be sent: the log is sent every third heartbeat cycle, which at a 26 s interval is about every 78 s. After more than 78 s the entry should be visible on the server with two times: the device time and the receipt time.

When comparing times, remember the time zones. The device time may be in UTC, while some tables keep local time, so a difference of 2 hours is a time zone shift, not a delay. Saving the log is safe for repeats thanks to the uniqueness of the pair of user and entry identifier, so the test can be repeated without the risk of duplicates.

Criteria for closing the deployment

The deployment is considered consistent when: all hosts respond correctly to the log endpoint, all watches report the target version, and the final test has produced an entry on the server. The result must be recorded in the acceptance protocol, so that in case of a dispute it is known when and who confirmed the state.

The queue window on the device is about 2 hours, so after updating a host that was blind, the watches may already have pushed out older entries. Do not count on filling in the history by a retrospective send: this is a window, not an archive.

Checklist

Video

Frequently asked questions

What does a 404 response from the log mean?

The host does not have the backend with this endpoint deployed and stays blind to the device log.

Where should the app version be taken from?

From the package manifest reported by the device management system, because other records may diverge.

After what time should the test entry appear?

After about 78 s at a 26 s interval, because the log is sent every third heartbeat.

Can the test be repeated?

Yes. The uniqueness of the pair of user and entry identifier prevents duplicates.

Let us plan the deployment acceptance

We will prepare an acceptance protocol for host and version checks matched to your network.

Let's talk