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  <20202021  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  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: RE: iocLogServer, logstash & procServ
From: 吴煊 via Tech-talk <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Wed, 10 Jun 2020 11:23:14 +0800 (GMT+08:00)
Hi all,
 I quote this message as I wish to know whether the issue of logstash dropping connection has been fixed, or how is it going on now.

Best regards,

Xuan

-----原始邮件-----
发件人:"Kivel Niko (PSI) via Tech-talk" <tech-talk at aps.anl.gov>
发送时间:2019-10-08 19:12:29 (星期二)
收件人: "Alfio Rizzo" <Alfio.Rizzo at esss.se>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
抄送:
主题: RE: iocLogServer, logstash & procServ

Hi Alfio

it's not an issue with logstash, the issue is in Epics base. To my best knowledge, Dirk is working on it. But, I'm not certain about the 'official' release status.
Right now we operate a fixed version of Epics base in production and I get north of 40k caPutLogs per hour w/o problems.
I use the ELK stack for syslog, caputlog and hardware monitoring through icinga2. The total index rate is about 100 /s and it's stable for weeks now.

Imho it's not a good idea to find a workaround, something as essential as logging should be properly implemented in base.

best
Niko

--
Paul Scherrer Institute
Dr. Niko Kivel
Forschungsstrasse 111
WBGB/014
5232 Villigen PSI
Switzerland

phone: +41 56 310 2226
email: niko.kivel at psi.ch

From: Tech-talk [tech-talk-bounces at aps.anl.gov] on behalf of Alfio Rizzo via Tech-talk [tech-talk at aps.anl.gov]
Sent: Tuesday, October 08, 2019 12:21
To: tech-talk at aps.anl.gov
Subject: iocLogServer, logstash & procServ

Hi,

I read that maybe iocLogServer will be dismissed and that logstash has some drop connection issue.

I am using instead procServ to listen on caPutLog port running a simple infinite-loop script.

In this way caPutLog write its output to procServ logfile.  

I think that procServ is good replacement for both iocLogServer and logstah, unless there are some advantages that the others have.

@Ralph, is there any option to make procServ to listen forever without the need to run any command (e.g. my infinite loop script)?    

Best

Alfio

 

PhD Alfio Rizzo

Control System Integrator

Integrated Control Systems Division

European Spallation Source ERIC

 

Telephone: +46(0)721792342

Mail Address: P.O Box 176, SE 221 00 Lund, Sweden

Visiting address: Odarslövsvägen 113, Lund

 

https://europeanspallationsource.se/

 

essLogo

 


Replies:
Re: iocLogServer, logstash & procServ Johnson, Andrew N. via Tech-talk

Navigate by Date:
Prev: Re: weird record names? Hu, Yong via Tech-talk
Next: Re: weird record names? Michael Davidsaver 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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: EPICS_BASE smart definition Konrad, Martin via Tech-talk
Next: Re: iocLogServer, logstash & procServ Johnson, Andrew N. 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  <20202021  2022  2023  2024 
ANJ, 11 Jun 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·