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: | Phoebus Alarm Server Kafka consumer client |
From: | John Dobbins via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Fri, 11 Dec 2020 02:27:49 +0000 |
All,
We are in the process of switching from the CSS Alarm Server which uses JMS to the Phoebus Alarm Server using Kafka.
For the old alarm server, I built a lightweight application which received server messages (via STOMP) and filtered them to pass along new alarms to SLACK. This is a stateless application, i.e. it doesn't try to maintain a list of PVs alarm states like the
CSS Alarm Display but just passes along notification of new alarms (filters out acknowledgements and transitions to OK). This has served us well - a notable exception being PVs which chatter in and out of alarm. Interested parties can then check alarms details
via CSS or web page. In the SLACK feed users may respond ("that was me doing x") or insert relevant data (plots, etc.)
I plan to do something similar for the new alarm server but wanted to inquire if anyone has already done something similar, has a Kafka consumer client which could be easily adapted, or has other ideas. The major constraint is that I don't have a lot of time
to work on this. 🙂
Thanks,
John Dobbins
Research Support Specialist
Cornell High Energy Synchrotron Source
Cornell University
|