Logging session / debug logs to stdout

vinylmike

1. Brekeke Product Name and Version:
3.14.7.4, Advanced

2. Java version:
openjdk-11-jdk

3. OS type and the version:
AWS ECS / docker - amzn2.x86_64

4. UA (phone), gateway or other hardware/software involved:
Freeswitch

5. Your problem:
Is there a way to configure Brekeke SIP Server to log to stdout instead of sip/WEB-INF/work/sv/log/2024? Specifically the SIP Session and Debug logs?

In an AWS ECS environment stdout / stderr gets logged/streamed to Cloudwatch.

Harold · Posted: Fri Feb 09, 2024 11:04 pm Post subject:

Add lines below in [Configuration]->[Advanced] page.

vinylmike · Posted: Tue Feb 13, 2024 9:24 am Post subject:

Thank you for the response. I have tried those settings and do see the log data is no longer being written to disk, but I also do not see anything in stdout.

Any thoughts?

Thanks,
Mike

Harold · Posted: Tue Feb 13, 2024 4:54 pm Post subject:

Also add this line in [Configuration]->[Advanced] page.

vinylmike · Posted: Tue Feb 13, 2024 5:38 pm Post subject:

Hi Harold,

Unfortunately that didn't help.

I've got the following in [Configuration]->[Advanced]:

Harold · Posted: Wed Feb 14, 2024 9:51 pm Post subject:

I confirmed that the settings above writes logs for stdout in Linux.

So I can see logs from the command below.
cat /proc/<pid>/fd/1

Harold · Posted: Wed Feb 14, 2024 9:59 pm Post subject:

Did you enable following logging Categories in [Diagnostics]->[Debug Logs] page?

SIP Session, Registrar

vinylmike · Posted: Thu Feb 15, 2024 11:47 am Post subject:

Hi Harold,

Thanks for the reply. Yes, SIP Session is checked in [Diagnostics]->[Debug Logs]. We're not using registration. Here's what I've discovered -

If I run a ps -ef on the Brekeke SIP Server process, it will yield something like this:

root 9564 8979 1 16:34 ? [truncated]
9564 is the PID
8979 is the PPID

If I "echo test >> /proc/8979/fd/1", I can see the entry using docker logs <container>, as well as in Cloudwatch. However, Brekeke is using PID, /proc/9564/fd/1, and those don't appear in Cloudwatch nor docker logs.

From the Tomcat point of view I've insured that it is configured to only log using ConsoleHandler.

Any thoughts on this?

Regards,
Mike

Harold · Posted: Sun Feb 18, 2024 9:30 pm Post subject:

If you run the ps command, there are several java processes, not only SIP Server.

You can check the SIP Server's PID at [PID] filed in [Status]->[SIP Server] page.

vinylmike · Posted: Thu Feb 22, 2024 9:59 am Post subject:

Hi Harold,

Yes, you're correct, I see the other java processes. The problem as I see it is that the Brekeke stream is not being outputted to the main process of the container (PID 1 inside the container). Docker only captures the stdout and stderr of the main process.

Thanks,
Mike

Harold · Posted: Thu Feb 22, 2024 2:45 pm Post subject:

If you use Linux as a host OS to run Docker, you can get a PID of a process running inside a Docker container.

With this PID, can you access to SIP Server's STDOUT?

vinylmike · Posted: Fri Feb 23, 2024 11:10 am Post subject:

Hi Harold,

Yes, I can get the PIDs -

vinylmike · Posted: Mon Mar 25, 2024 8:39 am Post subject:

I ended up with a sidecar approach, using fluentd. This appears to not be a Brekeke SIP Server issue and more with how docker/Cloudwatch work.

Thanks for your help.

Harold · Posted: Mon Mar 25, 2024 11:53 am Post subject:

Thank you for the update.