Recent Changes

Differences

This shows you the differences between two versions of the page.

--- dev:publisher:publisher_logging [2026/07/16 09:23]
pieter [Publication Monitoring Events]
+++ dev:publisher:publisher_logging [2026/07/16 09:31] (current)
pieter
@@ Line 6: / Line 6: @@
   * Database logging
-Some logging events can only be stored in a database, so need ''Database Logging'' to be enabled.
+Usage pages in the Console are only available when at least File logging is active.
+Some logging events can only be stored in a database, so need ''Database Logging'' to work.
   * Viewer Report a Problem
   * Viewer Photo Annotations Sidebar
-  * Viewer Telemetry (needs to be explicitly enabled as well)
+  * Viewer Telemetry
+Viewer Telemetry needs to be explicitly enabled from the Console System page.
 ===== Server Uptime =====
@@ Line 29: / Line 33: @@
 This table contains events that are valuable to an administrator.
-  * Login failure
+  * Failure to Create Guest session due to publication limit reached
-  * Failure to create Guest session
+  * Failure to Create Guest session due to server limit reached
-  * ...
+  * Login failure due to Wrong credentials
+  * Login failure due to No permission
+  * Publication session threshold warning reached
+  * Server session threshold warning reached
-Thresholds for some of these events can be configured in the Console System page.
+Session threshold warnings can be configured in the Console System page.
 ===== Publication Logins =====
@@ Line 65: / Line 72: @@
 Table: ''log_publisher_telemetry_events''
-Since version 26.2.0, you can enable Viewer Telemetry logging from the Console.  Once enabled, viewers that open after the setting was set to true, will post the following information :
+Since version 26.2.0, you can enable Viewer Telemetry logging from the Console.\\ Once enabled, viewers that open after the setting was set to true, will post the following information :
   * Open Workspace Timing
   * Open Resource Timing

Last modified:: 2026/07/16 09:23