Experimental Physics and
Industrial Control System

"Kivel Niko \(PSI\) via Tech-talk" <[email protected]> · Tue, 8 Oct 2019 11:12:29 +0000

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: [email protected]
________________________________
From: Tech-talk [[email protected]] on behalf of Alfio Rizzo via Tech-talk [[email protected]]
Sent: Tuesday, October 08, 2019 12:21
To: [email protected]
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]

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System