All docs

Upgrade, rollback and licensing

Upgrade bundles follow the same offline path as installation. Back up before upgrading; roll back if it fails.

Before upgrading

Export the current configuration
Confirm free storage
Confirm the license is still valid
Record the current version

Upgrade

Import the upgrade bundle
Verify signatures and digests
Roll components
Watch core's /readyz

Core may be briefly NotReady during the upgrade. That is expected. It will not report ready while dependencies are down.

Rollback

The platform can return to the previous version
Rollback uses the pre-upgrade backup
After rollback, confirm writes and queries are healthy

Agent rollback

Capture mode can be rolled back without swapping binaries:

collectors:
  traces:
    capture:
      mode: tc_ebpf

Write it to /etc/diting/agent.yaml and restart the agent. Valid values:

auto
tc_ebpf
socket_syscall
disabled

License

Offline file, asymmetric signature
Renew offline before expiry
No vendor server connection

Verify

After the upgrade check:

hosts online
recent traces continuous
logs still arriving
alert rules firing as expected

Related: Deploy and offline install, Troubleshooting.