Error reports via sending emails to operators #181
Replies: 1 comment 2 replies
-
This is a good idea. There is an existing hook that could be used for this, the sterp station program. A skeleton for that can be found in /usr2/st.default/st-0.0.0/sterp/. The skeleton just provides the structure, the code to report the errors has to be provided by the stations. Some stations already use this to make errors more visible for operators. Since sending email is fairly universally available, it may make sense to provide an example sterp that can do that. As you suggest, a control file would be desirable. Specifying the error codes that should have email sent could be similar to what is in erchk.ctl. Specifying email addresses would require an expansion. A first cut, which may be sufficient, could be send emails to all the addresses listed. (Note that the errors turned off with OTOH, maybe it would make sense to do something more modern and as a separate facility. You could have a program that subscribes to the display stream (which |
Beta Was this translation helpful? Give feedback.
-
FS
do provide a window to show various Errors. This requires operators to keep en eye on the window regularly. At Onsala, we run VLBI observations without dedicated operators. So, suport scientists have to monitor the status of VLBI observations remotely from time to time.Our antenna control software
BIFROST
has a function to send severe errors errors to support scientists via emails. This is a very helpful function for both developers and support scientists to test and monitor the system more efficently. Thus, I propose to implement a similar function to the future FS. The function may requires a new control file to define error types/codes and target email addresses.Beta Was this translation helpful? Give feedback.
All reactions