MEN-7288 - feat/threshold migration

[mzedel]

[mender-test-bot]

@mzedel, Let me know if you want to start the integration pipeline by mentioning me and the command "start pipeline".

---

my commands and options

You can trigger a pipeline on multiple prs with:

• mentioning me and start pipeline --pr mender/127 --pr mender-connect/255

You can start a fast pipeline, disabling full integration tests with:

• mentioning me and start pipeline --fast

You can trigger GitHub->GitLab branch sync with:

• mentioning me and sync

You can cherry pick to a given branch or branches with:

• mentioning me and:

 cherry-pick to:
 * 1.0.x
 * 2.0.x

[estenberg]

Looks good, just would clarify the "What's changing" part. In particular what does "detected" and "any contact with Mender" mean? I would perhaps make it a bit more technical so that it's more clear. Those people reading are pretty technical anyway. :)

[mzedel]

@estenberg thank you for looking into this! Would the following be enough?:

offline devices can only be filtered for after at least one full day without any API request to the Mender backend

[estenberg]

Better, but API request can mean many things, such as the user or UI making an API request..

Perhaps "For filtering / listing which devices are offline, the data filtered on may be up to one day old. In other words, if the device has been offline for a while and only recently contacted the Mender server, it may still be listed as offline until the data filtered on is updated (within 1 day)."

[estenberg]

Overall I feel this was a convoluted change (long time ago), that focused more on our infra performance than how it affected the user. It is what it is now, but we need to do better next time.

[mzedel]

Better, but API request can mean many things, such as the user or UI making an API request..

then maybe: offline devices can only be filtered for after at least one full day without any API request by a device to the Mender backend 🙃

Perhaps "For filtering / listing which devices are offline, the data filtered on may be up to one day old. In other words, if the device has been offline for a while and only recently contacted the Mender server, it may still be listed as offline until the data filtered on is updated (within 1 day)."

Afaik it is a bit the other way around: if the device has been offline for a few hours it won't be listed as offline before 1 day has passed, whereas if it was offline for a while, the device coming back online will be visible right away. Here a device coming back online means: any request to the API by a device.

[estenberg]

I am so confused by this. :-/

[estenberg]

Okey, let me try again:

"If a device no longer connects with the server, it may take up to 1 day until it is shown as an offline device in the UI."

[michaelntech]

Change to lowercase "c"

[michaelntech]

Maybe add to the start of this line:
"Offline threshold: if a device..."

Using the same name it has in the settings, so it is clear which setting this affects.

[michaelntech]

@mzedel here :)

[mender-test-bot]

Merging these commits will result in the following changelog entries:

Changelogs

gui (feat/threshold-migration)

New changes in gui since master:

Features

• added notification about changes to the device offline threshold
  (MEN-7288)

[mender-test-bot]

Hello 😺 This PR contains changelog entries. Please, verify the need of backporting it to the following release branches:
3.7.x (release 3.7.x)
3.6.x (release 3.6.x)