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: Alarm and logging systems
From: "Konrad, Martin via Tech-talk" <tech-talk at aps.anl.gov>
To: "Garrahan, Jacqueline" <jgarra at slac.stanford.edu>
Cc: EPICS Tech Talk <tech-talk at aps.anl.gov>
Date: Wed, 2 Sep 2020 13:57:41 +0000
Hi Jackie,
At FRIB we are currently moving from BEAST to the Phoebus Alarm Server.
In my experience the Phoebus alarm system is much more reliable than
BEAST and shows better behavior when used with larger numbers of alarms.

For logging we're using the ELK stack. So far our IOCs pass log messages
directly to a central log server (actually a cluster to improve
availability) through plain TCP connections. This is not ideal. If we
find the time we want to switch towards an approach that hands over log
messages to a proper logging service/library which takes care of
delivering them to the central log server (I remember Michael also had a
few lines of code to do so). This would be more reliable in case network
connections are interrupted temporarily. This would potentially also
come with the opportunity to store logs locally when the log server is
not available and transfer them once the log server is reachable again.

-Martin

-- 
Martin Konrad
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: konrad at frib.msu.edu

References:
Alarm and logging systems Garrahan, Jacqueline via Tech-talk

Navigate by Date:
Prev: How to handle adjusting values as they change independent of the driver in an asynPortDriver? Wlodek, Jakub via Tech-talk
Next: Re: How to handle adjusting values as they change independent of the driver in an asynPortDriver? Mark Rivers 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: Alarm and logging systems Jeong Han Lee via Tech-talk
Next: CAEN R1470ET HVPS - Asyn + Stream Device auto connect does not recover communication Paduan Donadio, Marcio 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, 02 Sep 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·