You are currently viewing the legacy RunMyJobs documentation site. This site will be taken down later this month.
All current and future RunMyJobs documentation, including versions 2023.3 and later, can be found here.
Please update your bookmarks. Use the version dropdown menu to select the documentation you need.

← JCS ErrorsGenDatabaseIndexes →

on-site-related topic Common Logging Categories

The following list describes the most used categories for tracing with the System_DynamicTrace process definition:

  • action - Actions and triggers
  • alert - Alerting (Active Monitoring Module)
  • infrastructure.logging.PerformanceLogger - performance tracing information
  • audit - Auditing (Active Auditing Module)
  • cluster - Cluster logging
  • connector - ERP Connectors
  • core - Core scheduler component
  • event - Events
  • jobchain - Chain
  • jobchainservice - JobChainService
  • jobservice - Generic jobservice, used by most components when running processes
  • mail - Mail Module
  • monitor - Monitor components
  • persistence - Database persistence
  • persistence.impl.PersistenceLogger.sqlhl - All high level SQL statements
  • persistence.impl.PersistenceLogger.sqlll - All SQL statements as sent to the database
  • persistence.impl.PersistenceLogger.tdump - transaction dumps of all transactions
  • persistence.impl.PersistenceLogger - all previous three (high level and low level SQL as well as transaction dumps)
  • remote - Remote API
  • script - Redwood Expression Language
  • scriptjobservice - Service for running scriptjobservice
  • security - security
  • systemjobservice - Systemjob service
  • ui - User Interface

The following categories can be used in the client-side JavaScript logger (for development only):

  • javascript
note

The JavaScript log is not produced by System_DynamicTrace.

The above logging categories can be used with the following log levels:

  • TRACE - the TRACE level (JavaScript/user interface only) designates very detailed informational events that are used by Redwood Server development to troubleshoot user interface issues.
  • DEBUG - the DEBUG Level designates detailed informational events that are most useful to debug an application.
  • ERROR - the ERROR level designates error events that potentially allow the application to continue running.
  • FATAL - the FATAL level designates very severe error events that potentially lead the application to abort.
  • INFO - the INFO level designates informational messages that highlight the progress of the application.
  • WARN - the WARN level designates potentially harmful situations.

See Also

onsiteTopic

← JCS ErrorsGenDatabaseIndexes →