locusworks/portal-webapp
3
0 Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Updated tex files with latest information about the program

Browse Source
This commit is contained in:
iparenteau committed 2026-09-04 17:15:15 -05:00
1 parent f0716b0073
commit 0f8db48407
91 files changed
+489 -822
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/src/guides/LogLevel.tex
+4 -4
View File
@@ -1,7 +1,7 @@
\section{Log Level Settings}
\label{logLevel}
The server uses loggers for server events. These logs are stored under \filename{\$PORTAL\_HOME/logs}; by default, \filename{\$PORTAL\_HOME} is \filename{\${user.home}/.portal}.
The server uses loggers for server events. These logs are stored under \filename{\$PORTAL\_HOME/logs}; by default, \filename{\$PORTAL\_HOME} is \filename{\${user.home}/.portal}.
Each application component has a logger associated with it with the default log level of \command{INFO} which will show general information to highlight progress. Each log level has an assigned level of importants with \command{OFF} being the most important and \command{ALL} being the least important. When determining what the log, the event to be logged compares itself to the logger and what its level is set at. If the event being logged is less important than the current log level for the component, that event will be ignored. If it is greater than or equal to the current level, the event will be logged.
@@ -27,7 +27,7 @@ The level of importances from greatest to least is
\subsection{Changing log levels}
The following case allows a user to change the log level for server components. Upon saving the log levels, the component will now respects its new level and log according.
NOTE: These values are persisted. Upon server restart, the server will see if there is an entry for the logger and set the log level accordingly; otherwise, it will use the default value. The location for the persisted portal logging file is \filename{\$PORTAL\_HOME/portal-loggers.properties}.
NOTE: These values are persisted. Upon server restart, the server will see if there is an entry for the logger and set the log level accordingly; otherwise, it will use the default value. The location for the persisted portal logging file is \filename{\$PORTAL\_HOME/portal-loggers.properties}.
When displaying the log levels, the levels are displayed in alphabetical order based off the component name
@@ -35,7 +35,7 @@ When displaying the log levels, the levels are displayed in alphabetical order b
\centering
\scalebox{0.75}{\includegraphics*{figures/menu.png}}
\caption{Menu}
\label{fig:menu}
\label{fig:menu-loglevel}
\end{figure}
\begin{figure}[!htp]
@@ -48,7 +48,7 @@ When displaying the log levels, the levels are displayed in alphabetical order b
\begin{usecase}
{CHANGE LOG LEVELS}
{Authenticated User with change log level permission}
{The user is viewing the log levels after selecting it from the menu. Reference figure~\ref{fig:hash-alg}}
{The user is viewing the log levels after selecting it from the menu. Reference figure~\ref{fig:log-levels}}
\begin{enumerate}
\item User pages through the tabs to find the component to change the log level
\item User chooses which level to set the log to (see table~\ref{tab:logLevels})