Comprehensive data protection for all workloads
Post Reply
christian.naenny
Enthusiast
Posts: 52
Liked: 14 times
Joined: Apr 08, 2015 11:52 am
Full Name: Christian Naenny
Location: Zurich, Switzerland
Contact:

Feature request: All logfiles in machine readable format

Post by christian.naenny »

Hello Veeam Development!
It would be extremely helpful for the task of analyzing the logfiles if it was possible to choose the format of the logfile to be XML, JSON or any other structured format!
It is rather difficult to parse the lines in log files like these (random example):

Code: Select all

[19.11.2025 22:35:57.432]    <18>    Info (3)    [SVccTransportClientGlobalCache] Initializing VCC transport client provider, reason: first initialization
[19.11.2025 22:35:57.432]    <18>    Info (5)    [ErrorDataConverter]    at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
[19.11.2025 22:35:57.432]    <18>    Info (5)       at System.Environment.get_StackTrace()
[19.11.2025 22:35:57.432]    <18>    Info (5)       at Veeam.Backup.Core.ExceptionSerialization.CCoreExceptionMapperFactory.CreateMapper(IScopedLogger logger, IExceptionModifier[] modifiers)
How do I know what still belongs to the same message? Do I have to implement a parser that is paying attention to the indentation - like in the last 2 lines? Is the indentation always going to be the same in all the logfiles? No, it's not!
I would really like the option to define the format of the logfile (XML|JSON|Text)
Thank you very much!
Best regards
Christian
Gostev
Chief Product Officer
Posts: 32902
Liked: 8058 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Feature request: All logfiles in machine readable format

Post by Gostev »

Hoi, Christian. I agree it would be nice but it also means rewriting logging for 20 years worth of functionality, which unfortunately is not going to happen as there will always be higher priorities. But our Support will be happy to assist you reading the particular logs in case you're experiencing an issue. Frankly speaking, debug logs were not designed to be used by end users in the first place, for example they were never proofread. Gruss Anton
Post Reply

Who is online

Users browsing this forum: Google [Bot], thosa, Yapman and 46 guests