Hello,
Here string values that appear to be GUIDs will be given the _g suffix and formatted as a GUID, even if the incoming value doesn't include dashes. For example, both "8145d822-13a7-44ad-859c-36f31a84f6dd" and "8145d82213a744ad859c36f31a84f6dd" will be stored as "8145d822-13a7-44ad-859c-36f31a84f6dd". The only differences between this and another string is the _g in the name and the insertion of dashes if they aren't provided in the input.
As of now there is no option to force custom suffix while generating logs. You can provide your feedback on this feature here in this feedback portal section.
Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.