I'm not sure I get the question around encoding/decoding logs. If the question is which format in which you'd store it, the answer is ideally something optimal for storage and efficient for machine consumption. So a binary or protobuf format is preferred over JSON.
As for error detection, yes, SHA-1 would work as well, but CRC is generally faster than computing cryptographic hash for something. So, prefer CRC.
what guideline can employed when trying to encode or decode logs ? also according to my findings on CRC as an error detection method . Can one use a normal checksum (SHA-1) for example to detect this
I'm not sure I get the question around encoding/decoding logs. If the question is which format in which you'd store it, the answer is ideally something optimal for storage and efficient for machine consumption. So a binary or protobuf format is preferred over JSON.
As for error detection, yes, SHA-1 would work as well, but CRC is generally faster than computing cryptographic hash for something. So, prefer CRC.
what guideline can employed when trying to encode or decode logs ? also according to my findings on CRC as an error detection method . Can one use a normal checksum (SHA-1) for example to detect this