Skip to main content
All CollectionsFAQProduct
Resolve Endpoint Conflicts in Level
Resolve Endpoint Conflicts in Level

Resolving UUID Conflicts in Level After Device Cloning

Updated over a week ago

Level generates a random UUID for each device during installation, ensuring there are no conflicts. The system retains this UUID even after agent reinstallation, preventing duplicate entries for the same endpoint.

However, if a device is cloned after Level has been installed, a UUID collision may occur, causing two devices to compete for the same entry in Level. To resolve this issue, you need to manually modify the UUID.

Automatic UUID Rotation

The simplest way to rotate the UUID is to use the built-in parameter. Running this command will automatically reset the UUID on the device and restart the Level agent so that change takes effect:

Windows Command

& 'C:\Program Files\Level\level.exe' --new-agent-id

macOS Command

sudo /usr/local/bin/level --new-agent-id

Linux Command

sudo /usr/local/bin/level --new-agent-id

Manual UUID Modification

Windows

  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Level

  • Key name: AgentID

macOS

  • Path: /Library/Application Support/Level/config.yaml

  • Key name: agent-id

Linux

  • Path: /etc/level/config.yaml

  • Key name: agent-id

After changing the UUID, restart Level to apply the changes.

Did this answer your question?