[srsran-users] logs related questions

[J Giovatto]

Hi,

Looking at lib/src/srslog/sinks/file_utils.h   it looks like the logger 
uses std::fwrite, so any delay will be associated with its behavior as 
far a I can see.

The log buffer for the EPC probably does not reach size needed to flush 
to the file while running, when the app closes any pending data is flushed.

You can lookup std::write buffering for more.

Well the brute force way would be to call flush after every write call, 
with expense of slowing down the application.

A better approach might be to create another type of sink (like a 
socket) for the logs/events you want to track and listen for those 
instead of parsing files.

Joe


On 5/2/24 05:13, Patrycja Palus (TME) wrote:
>
> •• PROTECTED 関係者外秘
>
>
> Hello all,
>
> I hope you all doing well! Currently I work on project, where I use 
> srsRAN as a network generator, but to improve it I create some scripts 
> to automate running the network. For that I need to analyse real time 
> logs, that are generated on eNB and EPC side. I'm trying to figure out 
> the logic that stands behind writing and savings logs, but I can't 
> recognize any pattern. So here are my questions:
>
> 1.
>     What is expected delay in writing logs? Other words, how much time
>     should I expect from the action from eNB/EPC to log to appear on
>     the log file?
> 2.
>     Why EPC logs appear only when I stop running EPC? So far, I don't
>     have any UE to connect, is there a chance that software needs to
>     run for longer to write down logs or there must be more lines to
>     be generated?
> 3.
>     Is there the way for me to configure somehow logs so I'm able to
>     set how often log file is refreshed with new lines? Or maybe there
>     is other way for me to capture logs before they appear in log files?
>
>
> I hope you can help me with solving my problems 🙂
>
> Br,
> Patrycja
>
> This e-mail may contain confidential information. If you are not an 
> addressee or otherwise authorised to receive this message, you should 
> not use, copy, disclose or take any action based on this e-mail. If 
> you have received this e-mail in error, please inform the sender 
> promptly and delete this message and any attachments immediately.
>
>
> _______________________________________________
> srsran-users mailing list
> srsran-users at lists.srsran.com
> https://lists.srsran.com/mailman/listinfo/srsran-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20240502/03700b69/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4079 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20240502/03700b69/attachment.bin>