# [LON-CAPA-cvs] cvs: loncom /html/adm/help/tex Domain_Configuration_Contact_Info.tex

raeburn raeburn at source.lon-capa.org
Sat Jan 30 22:44:05 EST 2021

raeburn		Sun Jan 31 03:44:05 2021 EDT

Modified files:
Log:
- Document domain configuration for "E-mail addresses and helpform"
- Whether error/status email should be sent to the core development group
- Weights to use when computing total error count for nightly status check
- Error count thresholds for sending nightly status email
- Exclude specific servers from contributing to "Unsent" updates total.

--- loncom/html/adm/help/tex/Domain_Configuration_Contact_Info.tex:1.6	Fri Oct 13 23:07:44 2017
+++ loncom/html/adm/help/tex/Domain_Configuration_Contact_Info.tex	Sun Jan 31 03:44:05 2021
@@ -22,12 +22,12 @@
release has been announced.
\item \textbf{LON-CAPA server status}
A nightly run of the /home/httpd/perl/loncron script will generate an e-mail
-if the weighted total of notices, warnings (weighted by 4), and errors
-(weighted by 100) exceeds a threshold of 200. The script checks load average,
-disk usage, and recent entries in the log files for the lond and lonc LON-CAPA
-daemons, as well as the difference between the number of delayed critical''
-transactions and the number of such transactions subsequently completed
-when connection was re-established, (as recorded in the permanent log file:
+if the weighted total of notices, warnings, and errors exceeds a specified
+threshold. The script checks load average, disk usage, and recent entries
+in the log files for the lond and lonc LON-CAPA daemons, as well as the
+difference between the number of delayed critical'' transactions and
+the number of such transactions subsequently completed when connection
+was re-established, (as recorded in the permanent log file:
/home/httpd/perl/logs/lonnet.perm.log).  If an e-mail is sent the message body
contains the same HTML as in the /lon-status/ page on each LON-CAPA server,
for which access is configured using the Display Detailed Report'' item
@@ -45,11 +45,45 @@
first installed) will continue to apply until the first {}Save''
of the Contact Information settings has occurred in the domain.

-Two additional settings allow you to indicate whether error reports should be
-sent to the LON-CAPA developers at Michigan State University (as well as to the
-recipients selected in your domain), and the same for an e-mail reporting a
-completed upgrade to a new LON-CAPA version. The default is to send both types of
-e-mail to the developers.
+Three additional settings allow you to specify:
+\begin{enumerate}
+\item Whether error reports submitted by users should be sent to the
+core developer group at Michigan State University (as well as to the
+recipients selected in your domain).
+\item Whether an e-mail reporting a completed upgrade to a new LON-CAPA version
+should be sent to the core developer group.
+\item Whether an email containing the nightly status report generated by
+loncron should be sent to the core developer group if the total error count
+exceeds a specified threshold.
+\end{enumerate}
+The default is to send all three types of e-mail to the core developer group.\\
+
+Settings for the nightly status check e-mail are also managed from
+the contact information screen.
+
+\begin{itemize}
+\item \textbf{Thresholds for error counts} can be set.  If the total error
+count exceeds the relevant threshold then email will be sent.  The default thresholds are:
+(a) 200 for status e-mail to be sent to designated recipient(s) in the domain,
+and (b) 2500 for staus e-mail to be sent to the core developer group.
+
+\item \textbf{Weights used to compute error count} can be set. The default weights
+are: Errors 100, Warnings 4, and Notices 1.  In addition, the default weight for
+Unsent critical' notifications to other LON-CAPA nodes is 5, but because unsent
+items are considered as Warnings, their effective weight is 5 x 4 (i.e., 20).
+
+\item \textbf{Servers with unsent updates to be excluded from count} can be set.
+
+An update' command will be sent to a LON-CAPA server subscribed to a resource,
+on republication of the resource.  If the server is uncontactable, the update will
+be stored as a delayed transaction, and will contribute to the Unsent total,
+unless the server is no longer present in the authoritative hosts table available
+from the consortium's name server(s).  If a specific server is still listed in the
+hosts table and is contributing to the overall error count, because there
+are update commands which have yet to be successfully sent, it can be explicitly
+excluded from adding to the count.
+\end{itemize}
+

\textbf{Configuration of the Ask helpdesk'' web form}, and who receives help request
e-mail is also done from the screen used to set contact information.