In debugging some recent issues with device emulation, I noticed that the device payload sent as a part of migration is not logged on the destination side if the import fails. We do have the payload from source logs, but it would be nice if, for debugging purposes, we also logged the payload that caused the failure in the destination logs.
In debugging some recent issues with device emulation, I noticed that the device payload sent as a part of migration is not logged on the destination side if the import fails. We do have the payload from source logs, but it would be nice if, for debugging purposes, we also logged the payload that caused the failure in the destination logs.