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: Phoebus Alarm Log panel |
From: | "Shroff, Kunal via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, William F Badgett Jr <badgett at fnal.gov> |
Date: | Mon, 9 Jan 2023 15:31:55 +0000 |
Hello William,
We recently upgraded the alarm-logger service to use elastic 8.
I have created a PR fixing the documentation (thanks for brining this to our attention) https://github.com/ControlSystemStudio/phoebus/pull/2501 Additionally, the Phoebus client was updated to use the REST interface to the alarm-logger service instead of directly querying elastic... this way in the future we should avoid the situation you are currently facing where the client needs to be updated everytime we have to upgrade or make changes to the backend.
If you want to migrate your data from the old elastic 6 backend to elastic 8 (except if you are running elastic in docker containers during the codeathon this was the one scenario we were not able to address)
Instructions for data migration are in this discussion https://github.com/ControlSystemStudio/epics-codeathon-2022/discussions/5 Cheers, Kunal From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of William F Badgett Jr via Tech-talk <tech-talk at aps.anl.gov>
Sent: 03 January 2023 16:45 To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: Phoebus Alarm Log panel Hello all,
I am trying to display Phoebus alarm-logger entries from an elastic-search instance using the "Alarm Log Table" panel.
I built Phoebus locally from the latest master branch on GitHub.com , but I'm getting errors from elastic-search, like:
2023-01-03 15:42:56 WARNING [org.phoebus.framework.jobs] Job 'searching alarm log messages for : *' failed
com.sun.jersey.api.client.UniformInterfaceException: GET
http://xxx.yyy.zzz:9201/search/alarm?current_message=*&severity=*¤t_severity=*&size=10000&pv=*&root=*&host=*&start=7+days&end=now&message=*&user=*&command=* returned a response status of 405 Method Not Allowed
Looking at the elastic-search with Kibana and curl, the data there look perfectly fine. We have tried elastic-search v6 and v7 with the same problem.
How do we get this work?
Thanks
William Badgett
Accelerator Division Controls
Neutrino Division Operations
Fermi National Accelerator Lab
Kirk and Wilson Roads
BTE-214 Booster Tower East Room 214
Batavia, IL 60510 U.S.A.
badgett at fnal.gov
|