I can understand the desire for consistency.

Unfortunately in our case we are using an external log service vendor and the 
application that is collecting the logs is provided by them. It simply collects 
all logs and does not have any option to preprocess individual log entries. We 
don’t have the ability to pre-process the logs prior to ingestion. We can, I 
think, filter out the extra info while searching the logs, but it will make the 
searches more complex and slower.

It would be nice to be able to disable this so there is some option to only log 
what is provided without manipulation. It could be a flag that affects xlog, or 
a different log function that doesn’t use the prefix. If you think it is 
worthy, I’d be happy to open a feature request.

Ben Newlin

From: Bogdan-Andrei Iancu <>
Date: Thursday, April 12, 2018 at 4:02 PM
To: OpenSIPS users mailling list <>, Ben Newlin 
Subject: Re: [OpenSIPS-Users] xlog adding information to output

Hi Ben,

Yes, this change was done on purpose for logs consistency reasons. As when you 
log via syslog you will get *all* the time the process name, pid and data as 
suffix, we considered that printing to strerr should follow the same model and 
have *all* the time the same prefix for the messages.

Now, I guess you grep the logs by some sort of an application (before having 
them pushed as jsons for later processing) - maybe you can do some extra 
pre-processing the strip the prefix before parsing it as json.


Bogdan-Andrei Iancu

OpenSIPS Founder and Developer<>

OpenSIPS Summit 2018<>
On 04/06/2018 10:58 PM, Ben Newlin wrote:

Yet another question. ☺

We use the json module to structure our output to and then print using xlog. 
Our log consumer processes the json format and can process and index our logs.

It appears that in 2.x the xlog module now always prepends a date string and 
the process number before every log. This is causing the logs to not be valid 
json format and they are not parsed properly by our consumer.

I know that OpenSIPS’ internal logs always print in this format with the date 
and process number in front. Was this an intentional change to make xlog print 
this way as well? Can it be disabled in any way?

I’m pretty sure I remember someone else asking about this not too long ago but 
I couldn’t find the thread in the archive.

Ben Newlin


Users mailing list<><>

Users mailing list

Reply via email to