Documentation

Appearance

Agent upgrade and removal ​

Treat the agent as a versioned field component with its own upgrade and recovery path. Do not assume that a Class Software release, OS image change, or dashboard setting upgrades the agent automatically.

Before you change a fleet ​

  1. Record the current agent version shown for a representative device.
  2. Confirm the supported upgrade path for the installed and target releases.
  3. Test on the same Linux image, architecture, and container runtime you ship.
  4. Verify Remote Shell, reconnect after reboot, logs or monitors you rely on, and any Class Software or stream-broker path you use.
  5. Roll out in bounded batches with a recovery plan.

Use the upgrade URL or procedure supplied for your current installation. Prefer the account-provided install or upgrade path over assembling packages by hand.

After an upgrade ​

On a staging device, run:

sh
dataplicity doctor
prelude-agent doctor

Confirm the device stays online, identity is unchanged, and product publishers still reach 127.0.0.1:18765 when you use Device Class streams. See Dataplicity agent for the on-device layout and checks.

Removal ​

Before removal:

  1. Confirm the correct procedure for the installed agent release and image.
  2. Make sure another local management path is available if the unit must remain operable without Dataplicity.
  3. Record any audit or support data your organisation must retain.
  4. Remove the device from fleet workflows that assume connectivity.
  5. Verify the device no longer appears available for remote operations.

Stop and disable agent services before deleting packages or users when your procedure requires that order. Remove supervisor packages, system users, shared directories, or container runtime changes only when the procedure for that installation explicitly requires it. Identity and state under /var/lib/dataplicity can retain credentials after services stop; treat those paths as secrets until wiped according to your decommissioning policy.

Contact support@dataplicity.com with the distribution, architecture, and installed agent release to receive the correct lifecycle instructions when the install path is unclear.