EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024 Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024
<== Date ==> <== Thread ==>

Subject: Re: IOC Logging
From: NICOLE Remi via Tech-talk <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Wed, 7 Feb 2024 13:10:47 +0000
Hey,

in our project, we are using systemd and journald for storing the logs,
by specifying '--logfile=-' in our procServ options.

Then, we use Loki[1] as log server, and Promtail[2] to upload the
journald logs to the Loki server.

If you use Docker, you can use the Docker driver[3].

[1]: https://grafana.com/oss/loki/
[2]: https://grafana.com/docs/loki/latest/send-data/promtail/
[3]: https://grafana.com/docs/loki/latest/send-data/docker-driver

It works quite well, you can set up alerts, and you also get the logs
of other systemd services. Useful for debugging if something goes
wrong.

Have a great day!
-- 
Rémi NICOLE <remi.nicole at cea.fr>
CEA/DRF/IRFU/DIS/LDISC

On Fri, 2024-01-26 at 16:02 +0100, Dr. Simon Friederich via Tech-talk
wrote:
>  Dear EPICS community,
>  I am currently investigating what options I have for storing the
> logs from our IOCs centrally. 
>  
>  I have set up a syslog-ng docker container for testing purposes. 
>  The host server has the IP 10.32.240.32, the docker container has
> published ports 514 (UDP), 601 (TCP).
>  
>  For testing purposes, I used a client in the same subnet with the
> command 
>      logger -n 10.32.240.32 "my_message"
>  successfully left a message.
>  
>  Now I have set the environment variables (on the client) in epics-
> base/configure/CONFIG_SITE_ENV.
>  EPICS_IOC_LOG_INET=10.32.240.32
>  EPICS_IOC_LOG_PORT=601
>  
>  In a simple test IOC on the client, I say 
>  iocLogInit()
>  and get the message
>  epics> log client: connected to log server at '10.32.240.32:601'
>  
>  I now wanted to test whether I can send a message with errlog:
>  epics> errlog("my message")
>  
>  However, after a short time (some seconds) I get:
>  epics> log client: lost contact with log server at
> '10.32.240.32:601'
>       because "Broken pipe"
>  
>  Then a short time later the IOC reconnects to the log server.
>  log client: connected to log server at '10.32.240.32:601'
>  
>  Have I overlooked something in the configuration?
>  I am also open to alternatives (e.g. logstash?). 
>  
>  Many thanks and best regards
>  Simon 

References:
IOC Logging Dr. Simon Friederich via Tech-talk

Navigate by Date:
Prev: Re: Seeking EPICS Database (.db) File Parser/Generator NICOLE Remi via Tech-talk
Next: Re: Seeking EPICS Database (.db) File Parser/Generator Ralph Lange via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024
Navigate by Thread:
Prev: Re: External: IOC Logging Niko Kivel via Tech-talk
Next: OpenSSL vulnerability epics Hermann, Raphael P. via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024
ANJ, 07 Feb 2024 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·