Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

newmember

Member

Registered: 2018-10-15

Posts: 34

Logging Suggestion / Idea

Just so that I can monitor the log files could we ask for the log files to follow a consistent format please.
Just an idea, the dash lines are nice but not required for monitoring, the lines that describe the process "File bin/pv yadyad" ....  not really easy to parse into a monitoring system.

Maybe follow a pattern like syslog

https://techzone.ergon.ch/syslog-message-format

Column 1 = "May 11 10:40:48"               > Timestamp
Column 2 = "scrooge"                       > Loghost
Column 3 = "disk-health-nurse[26783]:"     > Application/Process
Column 4 = "[ID 702911 user.error]"        > Syslog facility.level
Column 5 = "m:SY-mon-full-500"             > Message ID
Column 6 = "c:H : partition health..."     > Message [possibly including rid, sid, ip]

eg:
Date                        IP of where xsi is running     info or debug or error message   MessageID  Message its self in human format 
"May 11 10:40:48" IPof[local|remote]host Job# [info|debug|error] Message ID  Message

---------------------------------------------------------------------------------------------------------------------------------
2018-10-31T20:10:25|  Remote backup job exit status was:
---------------------------------------------------------------------------------------------------------------------------------
2018-10-31T20:10:25|  Original Unique Id (OUID):
---------------------------------------------------------------------------------------------------------------------------------
2018-10-31T20:10:25|  Cannot match current Session Id to parsed OUID var
---------------------------------------------------------------------------------------------------------------------------------
2018-10-31T21:00:19|  ###############################################################################
2018-10-31T21:00:19|     XSIBACKUP-PRO 11.1.4: new execution request
2018-10-31T21:00:19|  ###############################################################################
2018-10-31T21:00:20|
2018-10-31T21:00:20|  Info: XSIBACKUP-PRO will now try to determine the remote's XSIBACKUP-PRO installation point...
2018-10-31T21:00:20|  Tip: should this process take too long, use the --remote-xsipath argument to set it per backup job
---------------------------------------------------------------------------------------------------------------------------------
2018-10-31T21:00:22|  Found (c) XSIBackup installation. Remote path is set dynamically
2018-10-31T21:00:22|  Remote xsi path set to: /vmfs/volumes/4f6f3b6d-986a5ca4-a980-5cf3fc1d6c7e/xsi-dir
---------------------------------------------------------------------------------------------------------------------------------
2018-10-31T21:00:22|  Preparing to execute backup in remote server: 10.240.100.43:22
---------------------------------------------------------------------------------------------------------------------------------
File xsibackup already present at server 10.240.100.43
---------------------------------------------------------------------------------------------------------------------------------
File EULA already present at server 10.240.100.43
---------------------------------------------------------------------------------------------------------------------------------
File bin/xsidiff already present at server 10.240.100.43
---------------------------------------------------------------------------------------------------------------------------------
File bin/xsibackup-rsync already present at server 10.240.100.43
---------------------------------------------------------------------------------------------------------------------------------
File bin/pv already present at server 10.240.100.43

admin

Administrator

Registered: 2017-04-21

Posts: 2,057

Re: Logging Suggestion / Idea

Logs follow a consistent format, maybe it's not the consistent format that you would like it to be.

We believe standards are important and will consider your complaint as a feature request, we nevertheless have a number of them in the todo list.

Given the fact that no syslog client is available in ESXi and that some would need to be adapted or programmed from scratch, this could take some time.