Category · 281 properties

ServiceNow Logging & Debugging properties

These properties control logging, tracing, and debugging behavior across ServiceNow components, including settings for code-signing tracking and CMDB lifecycle utilities. Admins and developers can review them when investigating application behavior, configuring diagnostic output, or narrowing down issues; examples include CSM_debug_log and com.glide.codesigning.tracking.debug.

Most common namespaces: com.glide 36 com.snc 36 glide (other) 32 Other namespaces 13 glide.cmdb 10 hermes 8

`CSM_debug_log`	This boolean property activates detailed logging for Customer Service Management processes, aiding in diagnostics and issue resolution.
`cmdb.lifecycle.util.log.levels`	This property configures the logging verbosity for CMDB lifecycle utilities, with a default level of 'info' that balances detail and performance.
`com.glide.codesigning.strategy.java_stack`	This property configures the method used for determining the call stack in code signing operations, impacting how stack traces are generated.
`com.glide.codesigning.tracking.debug`	This property activates detailed debug logging for the code signing tracker, providing more information during code signing operations.
`com.glide.codesigning.tracking.logging.count`	It limits the number of logged code signing messages to a specified count over a daily period, helping to control log volume.
`com.glide.codesigning.tracking.logging.enabled`	This property activates logging specifically for tracking code signing actions within the ServiceNow platform.
`com.glide.cs.commons.trace_strategies`	This property configures the tracing strategies used for logging event data, allowing for either detailed end-to-end tracing or metric-focused logging.
`com.glide.cs.commons.tracer_enabled`	This property controls whether tracing is active for common service operations, allowing for enhanced logging and monitoring.
`com.glide.cs.debug.topicblocklogging.enabled`	This property controls the activation of topic block logging and validation, impacting how logs are recorded and validated in the system.
`com.glide.cs.enable_node_logging`	This property controls whether node details are logged during conversation tasks, impacting how information is stored and accessed for support and debugging.
`com.glide.cs.enable_node_logging.system_topics`	It configures the system to log node details in task context when processing VA system topics, aiding in diagnostics.
`com.glide.cs.publisher.debug`	This property, when set to true, allows for the inclusion of extra metadata in published topics, aiding in debugging efforts.
`com.glide.cs.unified_logging.store.app.enabled`	It controls the activation of logging features for store apps, ensuring backward compatibility with previous logging methods.
`com.glide.cs.worker.hybid_queue.verbose_logging`	This property activates verbose logging for the hybrid queue worker, providing more detailed output for diagnostics.
`com.glide.decision_table.debug_logging`	This property activates detailed logging for decision tables, providing insights into their execution and performance.
`com.glide.document.log.level`	This property configures the log level for document processing activities, impacting how much detail is recorded in the logs.
`com.glide.embedded_help.log_interval`	This property specifies the frequency, in hours, at which logs for Embedded Help are created, with a default setting of 6 hours.
`com.glide.embedded_help.logging_enabled`	This property enables or disables the logging of events related to Embedded Help, impacting how usage data is recorded.
`com.glide.financial_management.debug`	This boolean property activates debug logging for financial management, providing detailed output for diagnostics.
`com.glide.history_walker.max_history_count`	This property determines the maximum count of history records the checkpoint walker processes, influencing whether it uses the sys_audit or sys_history_set table for optimal performance.
`com.glide.hub.flow.approval.logging`	This property configures the logging level for Flow Designer approval actions, affecting how much detail is recorded in logs.
`com.glide.hub.flow_engine.listener_trace.threshold`	This property determines the minimum log level of messages that are replicated to the flow log, filtering out lower-level entries.
`com.glide.hub.flow_engine.log_level`	It determines the minimum log level for messages recorded in the sys_flow_log table during Flow Designer execution.
`com.glide.identity.security.impersonation.log.enabled`	This property controls whether impersonation logs are generated by the Identity Security API, providing visibility into impersonation actions.
`com.glide.import_set.importlog_level`	This property configures the level of detail in import set logs, allowing for INFO, WARNING, or ERROR levels to manage logging output effectively.
`com.glide.index_suggestion.debug`	This property activates detailed logging for the index suggestion feature, helping to identify and resolve potential issues.
`com.glide.one.extend.enable.debugging`	This property determines the logging level, allowing for performance or debug logs based on the specified value.
`com.glide.one_extend.mosaic_monitor.max_latency_minutes`	It defines the threshold for latency checks on Mosaic LLM invocation logs, determining when a response is flagged as high-latency.
`com.glide.one_extend.mosaic_monitor.window_minutes`	It specifies the number of minutes to look back for relevant log records when assessing latency in Mosaic LLM responses.
`com.glide.pad.core.runtime.variant_selector_threshold_time`	This property specifies the threshold time in milliseconds for logging warnings regarding the duration taken to select a variant for playbooks.
`com.glide.schedules.log.level`	This property configures the log level for the com.glide.schedules component, affecting the verbosity of log messages generated during schedule execution.
`com.glide.security.protected_table.include_source`	This property determines whether the source of update or delete operations on protected tables is included in log messages when logging is enabled.
`com.glide.servicecatalog.item_creator.factory.log`	It configures the logging level for item creation processes, allowing for different levels of detail in log outputs.
`com.glide.servicecatalog.item_creator.log`	This property configures the logging level for item creation events, allowing for different levels of detail in the logs.
`com.glide.servicecatalog.log`	This property configures the logging level for the service catalog, allowing for options such as 'info' to control the verbosity of log messages.
`com.glide.sys.log.source.enabled`	This property controls whether source logging is active, affecting the visibility of log entries related to their origin.
`com.glide.tracking.call_chain.enable_transaction_call_chain`	It configures the system to track transaction call chains, providing visibility into the sequence of operations during transactions.
`com.glide.ui.diagnostics.load_balancer.max_nginx_weight`	It configures the upper limit for the nginx weight shown in load balancer statistics, impacting how load distribution is monitored.
`com.glideapp.servicecatalog.log`	This property configures the logging level for service catalog operations, impacting the amount of detail captured in logs.
`com.snc.change_management.cab.log`	This property sets the logging level, with a default of 'Info', for the Change Management CAB Workbench, impacting the visibility of log messages.
`com.snc.change_management.core.log`	This property configures the logging level for change management, allowing for adjustments between different severity levels such as 'info' and 'warn'.
`com.snc.change_management.policy.approval.log`	This property configures the logging level for events related to Change Approval Policies, affecting how much detail is recorded in the logs.
`com.snc.core_automation.internal_client.log.debug.enabled`	It activates detailed logging for HTTP requests sent to internal services, aiding in the identification of errors or performance issues.
`com.snc.cs_base.log.verbosity`	This property configures the verbosity level of logs generated by the Code Search application, with options ranging from critical errors to detailed debug information.
`com.snc.csf.max.telemetry_queue_size`	This property defines the upper limit for the telemetry queue size, impacting how much telemetry data can be stored temporarily.
`com.snc.iam.log_level`	This property configures the logging level, allowing options such as debug, info, or error to control the detail of logged information.
`com.snc.integration.scim2.client.log.cleanup.duration`	This property sets the duration in days for which logs are kept before being automatically cleaned up, with a default of 180 days.
`com.snc.integration.scim2.client.log.request.status`	It configures the SCIM client to log either all request statuses or only failures, impacting the amount of log data generated.
`com.snc.integration.scim2.rte.verbose.logging.enabled`	Enabling this property activates detailed logging for SCIM User and Group RTE operations, providing insights into the integration processes.
`com.snc.ml_base.log.verbosity`	This property configures the verbosity level of logs generated by the ML Base project, allowing for different levels of detail from critical errors to detailed debugging information.
`com.snc.on_call_rotation.access.debug`	This property activates detailed logging for the on-call rotation feature, assisting in identifying and resolving issues.
`com.snc.on_call_rotation.log.level`	This property configures the verbosity of logs generated during On-Call rotation processes, impacting the amount of detail captured in logs.
`com.snc.on_call_rotation.log_escalations`	This property enables or disables the logging of escalation details within the on-call rotation feature.
`com.snc.pa.dm.syslog_minlevel`	This property configures the minimum severity level of logs that the system will capture, allowing for better management of log data.
`com.snc.pa.indicator_tags.log`	This property configures the verbosity of logs generated by the tagging UI, impacting how much information is recorded during operations.
`com.snc.pa.scores_migration.log_invalid_scores`	This property enables logging of invalid scores encountered during the migration of scores, aiding in identifying data issues.
`com.snc.pae.dashboard.logging`	This property controls the logging functionality for dashboards, allowing logs to be generated when enabled.
`com.snc.planned_task.debug`	This property controls whether debugging output for planned task scripts is displayed in the console, aiding in script development and issue resolution.
`com.snc.project.loglevel`	This property sets the verbosity of logging for project scripts, ranging from no logging to detailed task information.
`com.snc.ratemodel.loglevel`	This property configures the log level for the rate model, affecting the amount of detail captured in logs.
`com.snc.resourcemanagement.loglevel`	This property sets the logging level for Resource Management, allowing for no logging, info-level logging, or detailed debug logging.
`com.snc.roadmap.loglevel`	This property configures the logging level for the Timeline Visualization API, allowing for no logging, informational logging, or detailed debugging output.
`com.snc.samp.debug`	This property activates detailed logging for reconciliation processes, aiding in the identification of errors or discrepancies during software asset management.
`com.snc.sla.breakdown_processor.log`	This property configures the logging verbosity for the SLABreakdownProcessor, allowing for adjustments based on operational needs.
`com.snc.sla.calculatorng.log`	This property configures the logging level for SLACalculatorNG, allowing for different levels of log detail based on operational needs.
`com.snc.sla.condition.log`	This property configures the logging verbosity for SLAConditionBase, allowing for different levels of log detail based on operational needs.
`com.snc.sla.flow.log`	This property configures the logging level for TaskSLAFlow, allowing for different levels of log detail based on operational needs.
`com.snc.sla.log.destination`	This property configures the destination for logging output, allowing logs to be directed to either the database or other specified nodes.
`com.snc.sla.logging.excluded_field_types`	This property defines a list of field types that will not be logged during SLA tracking, enhancing data security.
`com.snc.sla.repair.log`	This property configures the logging level for SLARepair, with a default setting of Notice, influencing the detail of log entries generated during SLA processing.
`com.snc.sla.task_sla.log`	This property configures the logging level for TaskSLA, affecting the verbosity of logs generated during SLA processing.
`com.snc.sla.task_sla_controller.log`	This property configures the logging verbosity for the TaskSLAController, with a default level of Notice.
`com.snc.sla.task_sla_controller.timers`	This property activates all TaskSLAController timers, facilitating testing and debugging of SLA-related tasks.
`com.snc.trigger_rules.log.level`	This property configures the logging level for trigger rules, allowing for different levels of detail in log messages.
`com.snc.walker.default`	This property specifies the default walker implementation, allowing options like HISTORY, AUDIT, or CHECKPOINT to control data handling.
`diagnostics.autorefresh.page`	This property configures the auto-refresh interval for the system diagnostics page, allowing for timely updates on system performance.
`diagnostics.condition.logEntries`	This property defines a condition that flags the count of log entries within a 24-hour period, helping to manage log volume and system diagnostics.
`diagnostics.condition.node.status`	This property specifies the criteria for identifying when a node is considered to be in a non-operational state.
`enable_vdu_log_analysis`	This boolean property determines whether log analysis is performed in the VDU, impacting the ability to monitor and analyze logs effectively.
`evt_mgmt.log_alert_sysid_and_time`	This property configures the logging of sys-ids and timestamps associated with processed alerts in the alert management system.
`evt_mgmt.log_debug`	This property controls whether debugging logs are displayed, helping in diagnosing problems within the system.
`glide.activity.rule.exclude.document_tables.sys_audit_relation`	This property configures which tables are excluded from activity tracking for the sys_audit_relation event, allowing for granular control over audit relationships.
`glide.adaptive.auth.log.mfa.relax.event`	This property enables logging of MFA relaxation events, allowing administrators to monitor when MFA enforcement is bypassed.
`glide.adaptive.auth.log.success.event`	This property allows the logging of successful authentication events, which helps in tracking user access and enhancing security monitoring.
`glide.ais.event_queue_writable`	This property enables or disables the ability to write all AIS events to the system event queue, impacting event logging behavior.
`glide.ais.ingestion.feedback_logger_error`	This property configures the ingestion feedback logger to capture and log error messages, helping in identifying issues during data ingestion.
`glide.ais.ingestion.feedback_logger_info`	This property configures the ingestion feedback logger to capture and log informational messages, aiding in the visibility of the ingestion process.
`glide.ais.ingestion.feedback_logger_minor_error`	This property determines where minor error messages from the ingestion feedback logger are sent, defaulting to syslog.
`glide.ais.ingestion.feedback_logger_warn`	This property configures the logging behavior for warning messages during data ingestion processes.
`glide.ais.transaction_logger.enabled`	This property toggles the functionality of the AI search transaction logger, allowing administrators to capture detailed logs of AI search activities.
`glide.ais.update_event_queue_writable_disabled_ts`	This property stores the last disabled timestamp of the update event queue in UTC format, which is essential for maintaining accurate event logging.
`glide.amb.client.batch.logging.channels`	This property configures the channels for receiving batch logs generated by the AMB client, impacting log management and visibility.
`glide.amb.client.batch.logging.enabled`	This property controls whether client logs are sent to the server for analysis and record-keeping.
`glide.amb.client.batch.logging.startTime`	This property configures the start time for enabling batch logging, impacting how long the feature remains active before automatic deactivation.
`glide.amb.log.level`	This property configures the server's log level, determining the amount of detail recorded in logs.
`glide.atf.rest.log.header_blacklist`	It filters out specified headers from being logged in the Automated Test Framework, replacing their content with a security message.
`glide.audit.track_impersonation`	This property, when set to true, logs impersonation actions in the sys_audit table, linking them to the actual user performing the action.
`glide.authenticate.multisso.debug`	This property controls the activation of debug logging specifically for the Multi-Provider Single Sign-On integration, providing detailed logs when enabled.
`glide.authenticate.session_access.debug`	This property activates debug logging specifically for zero trust session access, providing detailed logs to assist in diagnosing authentication problems.
`glide.authenticate.sso.saml2.debug`	This property activates detailed logging for SAML 2.0 authentication processes, helping to identify and resolve login errors.
`glide.autodispatch.debug`	It configures the system to output debug logs for the auto dispatch engine when tasks are assigned, aiding in diagnostics.
`glide.awa.default_logging_duration`	This property determines the default time limit for logging activity in AWA Service Channels, stopping after the specified duration.
`glide.businessrule.callstack`	This property controls the logging of business rule executions, allowing administrators to track when business rules start and finish.
`glide.canonical_name.enable.logging`	This property controls the logging behavior for company normalization processes, allowing for better tracking and debugging of related operations.
`glide.cluster.xmlstats`	This property configures the components, such as scheduler and memory, that are logged in the cluster state for performance tracking.
`glide.cmdb.canonical.log`	This property controls whether logging is enabled for canonical data management activities, helping track changes and issues.
`glide.cmdb.logger.source.AnomalyScoreProcessor`	It configures the logging levels for the anomaly score processor, allowing for info, warn, and error messages to be recorded.
`glide.cmdb.logger.source.CMDBDependentCIProcessor`	It configures the logging levels, allowing for error, warning, informational, debug, and verbose debug messages to be captured during the operation of the CMDB dependent CI processor.
`glide.cmdb.logger.source.cmdb_dedup_template`	It defines a comma-separated list of logging levels, including info, warn, error, and debug, for De-Duplication templates.
`glide.cmdb.logger.source.cmdb_multisource`	This property configures the logging level for CMDB 360, allowing for different verbosity levels such as info, warn, error, debug, or debugVerbose.
`glide.cmdb.logger.use_syslog.AnomalyScoreProcessor`	This property specifies the logging levels—info, warn, and error—used by the CMDB anomaly score processor to report its activities.
`glide.cmdb.logger.use_syslog.CMDBDependentCIProcessor`	This property specifies the logging levels, such as error, warn, info, debug, and debugVerbose, for the CMDB dependent CI processor's syslog output.
`glide.cmdb.logger.use_syslog.CMDBHealth`	This property specifies which levels of logging are recorded for CMDB health, allowing for more detailed monitoring based on the configured values.
`glide.cmdb.logger.use_syslog.Duplicate_Merger`	This property specifies the logging levels—info, warn, and error—for duplicate merger activities in the CMDB.
`glide.cmdb.logger.use_syslog.cmdb_dedup_template`	This property defines a comma-separated list of logging levels, such as info, warn, and error, specifically for De-Duplication templates.
`glide.cost_mgmt.debug`	This property activates detailed logging of cost management processes, which can assist in identifying issues during development or maintenance.
`glide.cs.debug`	When enabled, this property directs the system to send debug logs to a specified channel for easier monitoring and troubleshooting.
`glide.cs.preview.log_filter`	This property configures the log filtering mechanism to prevent specific log entries from being sent to the AMB channel.
`glide.db.audit.ignore.delete`	This property allows administrators to define a comma-separated list of tables that are excluded from deletion auditing, impacting how deletions are tracked in the system.
`glide.db.audit.lazy`	This property controls the immediate creation of audit records in relation to transaction changes, impacting the reliability of audit trails.
`glide.db.loguser`	This property disables the rendering of SQL error messages in the browser, enhancing security by preventing exposure of sensitive database details.
`glide.db.stats`	When enabled, this property logs queries that exceed the duration specified by glide.db.stats.threshold, helping to identify performance bottlenecks.
`glide.db.upgrade.log.save_to_db.enabled`	This property enables the saving of upgrade log messages to the database, facilitating access to upgrade logs through the upgrade history.
`glide.debug.log_point`	This property enables or disables the log points feature, affecting how logs are generated during debugging sessions.
`glide.debug.trace.trace_line_limit`	This property limits the number of trace statements displayed, helping to control output volume during debugging sessions.
`glide.debugger.log.ui`	This property configures the user interface options for viewing logs in the script debugger, affecting how information is displayed to users.
`glide.diagnostic.page./replication.do`	This property defines the class responsible for processing requests directed at the /replication.do URL, impacting how replication statistics are retrieved.
`glide.discovery.debug.network_discovery`	This property activates extensive logging for network discovery processes, aiding in troubleshooting and monitoring network activities.
`glide.discovery.identification.log_level`	This property configures the log level for the identification engine, allowing options like Info, Warn, Error, Debug, DebugVerbose, and DebugObnoxious to manage log detail.
`glide.discovery.ire_err_exclusion_list`	It specifies which IRE error enums are excluded from logging, helping to reduce noise in the logs.
`glide.discovery.log_sensor_metrics`	This property activates the recording of sensor execution times in the Discovery Metrics table, providing insights into sensor performance.
`glide.discovery.save_pattern_log`	This property controls the saving of pattern logs after successful pattern execution, impacting performance and diagnostic analysis.
`glide.discovery.sensors.debugging`	This property activates debugging for sensors, allowing detailed logging and diagnostics to assist in identifying issues.
`glide.escalation.verbose`	This property configures the system to log verbose messages related to escalations, providing more detailed information during these events.
`glide.graphql.debug`	This property controls the activation of debug logging for GraphQL, allowing detailed logs to be generated for analysis.
`glide.hermes.debug.enabled`	This property enables or disables debugging logs specifically for the Hermes application, providing detailed logs when set to true.
`glide.html_sanitize.discarded_log.enable`	This property enables or disables logging of HTML sanitization events in the sys_log table, impacting security monitoring capabilities.
`glide.http_event_watch.enabled`	This property determines whether HTTP event watching is active, impacting how the system logs and responds to HTTP requests.
`glide.hub.process.sync.debug`	This property enables detailed debug logging for synchronization processes, helping to diagnose issues during data synchronization.
`glide.identification_logs.max_run_ids`	This property defines the upper limit of log runs shown when accessing Configuration > Identification Logs, with a default value of 1000.
`glide.ih.kafka.consumer.log_empty_stats`	This property controls the logging of empty consumer statistics, allowing or preventing logs when no messages are processed during the defined interval.
`glide.ih.kafka.consumer.log_interval`	This property determines how often consumer statistics are logged, allowing for monitoring of message consumption and production activity over specified intervals.
`glide.ih.kafka.producer.message_bytes_to_log`	This property configures the byte limit for logging Kafka producer message content, allowing for controlled visibility of message details in logs.
`glide.ih.kafka.stream_connect.debug`	This property activates detailed logging for Stream Connect, allowing for better visibility into message replication processes.
`glide.importlog.log_to_table`	When enabled, this property logs information-level messages related to import processes into the import_log table, aiding in monitoring and debugging.
`glide.les.disable_logs_forwarding`	This property disables log forwarding in the Log Export Service when set to true, ensuring no logs are sent during critical database operations.
`glide.log.client.script.on.change`	This property determines whether changes to client scripts are logged, providing visibility into script modifications.
`glide.log.client.script.on.load`	This property determines whether client script logs are generated during form load events, aiding in debugging and performance analysis.
`glide.log.client.ui.policy`	This boolean property determines whether client-side UI policy actions are logged, affecting the visibility of UI policy execution in logs.
`glide.log.directory`	This property defines the directory path where log files are stored, impacting log file accessibility and organization.
`glide.log.formatter`	This property configures the log formatter class, affecting how log messages are formatted and displayed in the system.
`glide.logfilemonitor.nextlines`	This property configures the logfile monitor to return a specified number of lines following a match, enhancing the visibility of log context.
`glide.logfilemonitor.prevlines`	This property configures the logfile monitor to return a specified number of preceding lines before a matched log entry is displayed.
`glide.notification.provider.debug`	This property activates detailed logging for notification providers, helping to identify issues during notification delivery.
`glide.notify.debug`	This property, when set to true, generates comprehensive logs for errors encountered during Notify workflows, aiding in troubleshooting and diagnostics.
`glide.outbound_http.db.log`	This property configures the system to log outbound HTTP requests in the database, facilitating monitoring and troubleshooting.
`glide.outbound_http.file.log.allow.all.fields`	This property enables or disables the logging of all fields in outbound HTTP requests, affecting the level of detail captured in logs.
`glide.outbound_http.security.log.allow.all.fields`	This property configures the logging behavior for outbound HTTP security events, allowing all fields to be included in the logs if enabled.
`glide.outbound_http.text.content_types`	This property allows the configuration of a comma-separated list of additional content types for logging, supplementing the default system-defined types.
`glide.outbound_http_log.override`	This property, when set to true, allows customization of the logging behavior for outbound HTTP requests, impacting how logs are recorded.
`glide.outbound_http_log.override.level`	This property configures the verbosity of logs generated for outbound HTTP requests, impacting how much detail is recorded.
`glide.outbound_http_log.security.restricted.fields`	This property configures a list of fields that are not logged for outbound HTTP requests, enhancing security by preventing sensitive data exposure.
`glide.parameter.dump.table_denylist`	This property defines which tables are excluded from logging to protect sensitive information.
`glide.quota.manager.debug`	This property controls whether to show detailed debugging information about transactions managed by the Quota Manager, including their status and quota matches.
`glide.rest.debug`	This property activates detailed logging for REST API interactions, aiding in the identification of issues during development and testing.
`glide.sc.log.variable_actions`	This property logs client-side actions on variables, providing visibility into user interactions and changes.
`glide.sc.mobile_layout_sync.log`	This property configures the logging level for mobile layout synchronization, allowing for different levels of detail in log entries.
`glide.schedules.log.debug`	This property activates detailed logging for schedule-related processes, helping identify issues during execution.
`glide.script.vtable.log.debug`	This property activates logging for remote table scripts, allowing detailed debugging information to be captured during script execution.
`glide.secure_cookie.debug`	This property activates detailed logging for operations involving secure session cookies, aiding in debugging efforts.
`glide.security.csrf.processor.all.authenticated.logging_enabled`	It activates logging for Cross-Site Request Forgery violations in authenticated sessions, helping to track potential security threats.
`glide.secury.event.send.forced`	This property, when set to true, forces the sending of events regardless of other conditions that might normally prevent them.
`glide.signals.handle_unknown_event`	This property configures the handling of unknown events by specifying whether they should be logged to all destinations or ignored.
`glide.soap.large_payload_log_threshold`	This property defines the size in MB at which SOAP request bodies are logged as large, enabling better tracking of potentially problematic requests.
`glide.sso.acr.debug.log.enabled`	It configures the system to include account recovery information in debug logs, aiding in troubleshooting and monitoring.
`glide.sys.audit_currency_value`	This property configures the format of currency values in audit records, allowing them to be stored with the currency code instead of just the numeric value.
`glide.sys.audit_inserts`	This property determines whether audit records are generated for the initial values of newly inserted records, providing a historical reference for data changes.
`glide.sys.domain.verbose`	It activates detailed domain logging and debug messages, which assist in identifying and resolving domain separation issues.
`glide.sys.log_impersonation`	This property controls whether impersonation events are logged for interactive sessions, helping to track user actions and enhance security monitoring.
`glide.sys.log_impersonation.non_interactive`	This property activates or deactivates logging for impersonations occurring in non-interactive sessions, allowing for better tracking of automated processes.
`glide.sys.log_impersonation.non_interactive.exclusion`	It allows administrators to specify users whose non-interactive impersonation sessions will not be logged, enhancing the clarity of audit trails.
`glide.sys.oracle.metrics1`	This property configures the specific metrics collected from the Oracle server, impacting performance monitoring and analysis.
`glide.system.error.url`	This property sets the application URL for processing glide system error codes, ensuring users are directed to the correct error handling page.
`glide.ui.audit_deleted_tables`	This property configures a list of system tables that will have delete operations logged for auditing purposes, which is not enabled by default.
`glide.ui.js_error_notify`	This property determines whether client script errors are displayed to client_script_admin users and a generic message to other users, enhancing error management.
`glide.ui.template.trace`	This property, when set to true, allows for the tracing of Jelly evaluations, sending the output to the log for review.
`glide.ui.ui_policy_debug`	This property controls whether UI policy processing events are logged in the JavaScript debug window, aiding in the diagnosis of UI behavior.
`glide.upgrade.blame.logger.debug`	This property activates detailed debug logging for the upgrade blame tool, providing more information during the upgrade process.
`glide.upgrade.blame.logger.enable`	This property enables the upgrade blame tool to assist in diagnosing problems that occur during system upgrades.
`glide.upgrade.log.enable`	This property controls whether the upgrade history log is active, providing a record of changes during system upgrades.
`glide.ux.banner_announcement.metrics`	When enabled, this property logs performance metrics related to the banner announcement API in the syslog table, helping track its performance.
`glide.uxf.lib.ux.metrics.level`	This property configures the level of metrics detail for UXF instrumentation, allowing values from 0 to 5 to be selected based on the desired granularity.
`glide.workflow.log`	This property controls whether detailed logs of workflow actions are recorded, aiding in debugging and performance analysis.
`glide.workflow.log.debug`	This property activates detailed logging for workflow processes, allowing for the capture of debug information.
`glide.workflow.log.error`	This property configures the system to log error messages generated by workflows, aiding in error tracking and resolution.
`glide.workflow.log.info`	This property controls whether workflow info messages are logged, providing insights into workflow execution.
`glide.workflow.log.warn`	This property controls whether warning messages related to workflows are logged in the system.
`hermes.collect.kafka.client.metrics`	This boolean property enables or disables the collection of metrics from the Hermes Kafka client, impacting performance monitoring capabilities.
`hermes.consumer.group.metrics.list`	This property defines a comma-separated list of metrics, such as join-rate and sync-rate, that are tracked for Kafka consumer groups.
`hermes.consumer.metrics.list`	This property specifies the metrics that are summarized for Kafka consumer clients, impacting performance monitoring and analysis.
`hermes.consumer.topic.metrics.list`	This property specifies the metric names that the Hermes Kafka Consumer client will use to report performance statistics.
`hermes.consumer.topic.partition.metrics.list`	This property configures the list of metrics, such as average and maximum record lag, that the Kafka consumer client will track for each topic partition.
`hermes.metrics.list`	This property specifies which GCF metrics are collected and reported, impacting performance monitoring and analysis.
`hermes.producer.metrics.list`	This property specifies which Kafka producer client metrics are collected and reported, impacting performance monitoring and analysis.
`hermes.producer.topic.metrics.list`	This property specifies which metrics, such as byte-rate and record-error-rate, are reported by the Kafka producer client for monitoring purposes.
`hermesgcfmetricsmasterlist`	It specifies which GCF metrics are collected and reported within the system.
`mid.log.command_audit.enable`	This property enables logging of commands run by the MID Server, capturing details such as command names, hashes, and execution status.
`mid.log.level`	It configures the logging level of the MID Server, with options including debug, info, warn, and error, affecting the detail of logs generated.
`mid.property.powershell.ih.log_level`	This property specifies the threshold for logging messages, allowing only those at the defined level or higher to be recorded.
`mid.property.powershell.log_info`	This property activates logging for PowerShell scripts, allowing developers to capture and view debug messages during execution.
`mid.server.rba_debug_powershell`	This property activates probe-level debugging for PowerShell probes, allowing for detailed logging of their activities.
`mid.server.rba_debug_ssh`	This property activates or deactivates debugging for SSH probes, providing detailed logs for troubleshooting.
`mid.sm.discolog.max_object_size`	This property limits the character size of objects in the Horizontal Discovery Log, affecting how much detail is captured in log entries.
`mid_server.cluster.debug`	This property activates detailed logging for the MID server cluster, helping to diagnose issues or monitor performance.
`pdi.analytics.app.list`	This property configures the application list for PDI Analytics, detailing paths and computed app counts for various studios.
`sa.debugger.max_timeout`	This property defines the maximum allowable time in seconds before a Pattern Debugger session times out due to inactivity, with a default of 240 seconds.
`sa.ie.log.ie_severity_level`	This property configures the logging severity level for the Identification Engine, affecting the amount of detail captured in logs.
`sa.ie.log.service_cache_severity_level`	It configures the severity level of logs generated by the service cache in the Identification Engine, impacting the amount of detail captured in log files.
`sa.network_path_calculator.verbose`	This property toggles verbose logging for network path calculations, helping to identify and resolve potential network issues more effectively.
`sn.metadata.tracing.enabled`	This property determines whether metadata tracing is active, impacting how changes are logged and monitored in the system.
`sn.metadata.tracing.table.records.expiration.days`	It sets the retention period for traced metadata records to a specified number of days, with a default of 90 days.
`sn_analytics_api.com.glide.ci.analytics.api.log_level`	This property configures the log level for the User Experience Analytics API, affecting the detail of log output generated by the system.
`sn_appauthor.logging.destination`	This property determines whether logging for scoped app clients is directed to the file system or the database, impacting how logs are accessed and managed.
`sn_appauthor.logging.verbosity`	This property determines the verbosity of logging, allowing options such as debug, info, warn, and error to be selected.
`sn_appclient.logging.destination`	This property determines whether logs for the scoped app client are saved to the file system or the database, with a default setting of FILE.
`sn_appclient.logging.verbosity`	This property configures the logging verbosity, allowing options such as debug, info, warn, and error to control log output.
`sn_apptmnt_booking.logging.verbosity`	This property sets the verbosity level of logs generated during appointment booking operations, allowing for different levels of detail based on the selected choice.
`sn_atf.debug`	This property activates additional debugging options, including a debugging tab on the Test Runner UI and the ability to save UI test result JSON to the test result record.
`sn_atf.metadata_tracing.caches_to_flush`	This property lists the caches that need to be flushed to enable effective ATF Metadata tracing for executed metadata.
`sn_capi.success_log_cleanup`	This property specifies the number of days to keep success logs generated by the Cloud API.
`sn_capi.trail_error_cleanup`	This property specifies the number of days to persist Cloud API trail error logs before they are automatically deleted.
`sn_ci_analytics.logging.verbosity`	This property configures the logging verbosity level for the Conversational Analytics application, impacting the detail of logs generated.
`sn_cld_intg_core.execution.log.sn_cld_intg_core_execution.level`	This property sets the default log level for execution events, with options to override it for specific execution tables.
`sn_cld_intg_core.execution.log.syslog.replicate`	This property determines whether execution logs are sent to syslog for replication, facilitating centralized log management.
`sn_cmp.success_log_cleanup`	This property configures the retention period for success logs, automatically deleting logs older than the specified number of days.
`sn_cmp.trail_error_cleanup`	This property configures the retention period for Cloud Orchestration trail error logs, defaulting to 30 days.
`sn_codesearch.logging.destination`	This property configures the destination for log messages generated by the Code Search application, allowing logs to be saved to the local node log or the database.
`sn_codesearch.logging.verbosity`	This property configures the verbosity level of logs for the Code Search application, allowing options from no logs to detailed debugging information.
`sn_communities.days_to_keep_search_logs`	This property determines how long search logs are kept in the system, allowing community admins to customize log retention periods.
`sn_communities.log.verbosity`	This property configures the verbosity of logs generated by the Code Search feature, allowing for different levels of detail from critical errors to detailed debugging information.
`sn_communities.logging.verbosity`	This property configures the verbosity of logging for the Code Search feature, allowing logs to display varying levels of detail from errors to debug information.
`sn_communities.view_log_sources`	It provides a structured mapping of various view log sources to static types, ensuring consistent logging in the Communities application.
`sn_config_hub.errorslogs.card.visible`	This boolean property controls the visibility of the error logs card within the Configuration Hub, affecting how administrators access error information.
`sn_devops.devops_log_level`	This property allows selection of the log level from options such as Error, Warning, Information, Debug, or Trace, influencing the detail of log output.
`sn_devops.enable_debug`	This property previously enabled debug logging for the DevOps application but is now deprecated in favor of a more flexible log level configuration.
`sn_devops.logging.destination`	This property configures where DevOps logs are sent, allowing for flexibility in log management and storage.
`sn_disco_workspace.enable_error_framework`	This property determines whether the Error Framework is used to capture and display Discovery errors in the Discovery Admin Workspace.
`sn_docs.enable_debug_logging`	This property controls the activation of debug logging for the sn-docs application, allowing for detailed logging information during operation.
`sn_ex_emp_fd.performance_stat_time_window`	This property configures the duration in seconds for which portal performance logging is disabled, impacting how performance data is recorded.
`sn_fsm.wm_weekly_resource_span_enable_log`	This property configures the logging of weekly resource span events, providing insights into resource usage and allocation.
`sn_fsm_map_integr.enable_map_provider_logging`	This property activates logging for map provider interactions, helping to capture detailed information for diagnostics.
`sn_fsm_map_integr.logging.verbosity`	This property configures the verbosity of logging for map integration processes, affecting the amount of detail captured in logs.
`sn_fsm_parts_src.logging.verbosity`	This property determines the logging verbosity level, allowing options such as debug, info, warn, and error to manage log output effectively.
`sn_fsm_sched_flws.logging_debug`	This property activates detailed debug logging for Field Service Management scheduling flows, helping to identify and resolve issues during flow execution.
`sn_gamification.enable_debug_logs`	This property toggles the activation of debug logs specifically for the gamification feature, aiding in diagnostics.
`sn_grc.common_item_logging_enabled`	This property activates logging for common item inheritance, allowing tracking of changes and usage within the GRC module.
`sn_hr_core.log`	This property configures the detail level of logs, with options ranging from 'Info' to 'Debug', affecting how much information is recorded during operations.
`sn_hr_ef.enable_purge_logs`	This property determines whether a log is generated for documents deleted during the employee document purge process.
`sn_hr_ef.purge_log_fields_to_include`	This property allows administrators to define specific fields that will appear in the purge logs for deleted documents, enhancing the clarity of the logs.
`sn_hr_le.log_level`	This property specifies the types of logs written to the HR Lifecycle Events Case Logs table, with options ranging from no logs to detailed debug information.
`sn_ia_config.log.level`	This property defines the logging level for Implementation Agent messages, allowing for different levels of detail such as Debug, Info, Warning, or Error.
`sn_itom_integ_app.overview_page_log_source_time_threshold_hours`	It configures the threshold for displaying a warning message based on the time elapsed since the last log source update.
`sn_itom_pattern.log_gcp_event_job`	This property controls whether account information is logged for the GCP-Events-job scheduled job, impacting the visibility of GCP event processing.
`sn_itom_pattern.logger_level`	This property configures the logging level, with a default of 'info', affecting the amount of detail captured in logs for the patterns application.
`sn_kmf.resolution_framework.audit_source`	This property specifies whether Resolution Framework records are logged to a table, system logs, or both, impacting how audit information is stored and accessed.
`sn_nxui_framework.logging.enabled`	This property controls whether UI Logging is active, impacting the ability to track user interactions and system events.
`sn_nxui_framework.logging.level`	This property determines the minimum log level captured by the UI Logger, affecting which console logs are recorded based on the specified level.
`sn_occ.log_viewer.max.characters`	This property configures the character limit for fields in the Log Viewer, affecting how much data is visible at once.
`sn_openframe.logger.enabled.users`	This property enables the logging of Openframe events for designated users by listing their sys_ids, allowing for targeted log persistence.
`sn_shop.log.property`	This property configures the verbosity of logs generated during Purchase Requisition Automation, impacting how much detail is recorded.
`sn_sm_scoped_app.sa.asc.logger_level`	This property configures the logging level for the Automated Service Suggestions feature, impacting the verbosity of log messages generated during its operation.
`sn_sm_scoped_app.sm_plus_logger.logger_level`	This property defines the minimal log level, such as error, that the SmPlusLogger will record, impacting the visibility of log entries.
`sn_sow_chg.change_conflict_calendar.log`	This property sets the logging level for the Change Conflict Calendar, with a default value of 'info' to capture relevant events.
`sn_sow_exp_app.view_user_mapping.wait_time_for_new_health_event`	It configures the duration to wait before a new health event is generated when the express list view-user mapping job encounters a failure.
`sn_sow_on_call.com.snc.on_call_rotation.log.level`	This property configures the logging level, with a default value of 'info', impacting the detail of log messages generated by the On Call Scheduling application.
`sn_sym_dlp.logging.verbosity`	This property configures the verbosity level of logs produced by the Symantec DLP integration, affecting the amount of detail captured in log files.
`sn_task_grouping.log.verbosity`	This property determines whether Task Grouping logs are displayed to users, affecting how much detail is available for task bundling operations.
`sn_task_recommend.logging_level`	This property configures the verbosity of logs generated during the Intelligent Task Recommendations process, affecting how much detail is recorded.
`sn_uxa_req_manager.analytics.queryservice.api.logging.level`	This property configures the log level for the Query Service, influencing the amount of detail captured in logs.
`sn_va_bot_ic.bot_interconnect.enable.logging`	This property activates debug logging for Bot Interconnect, allowing for detailed tracking of conversations and system behavior.
`watson_assistant.nodes_visited_details`	This property, when set to true, provides detailed diagnostics about the dialog nodes visited during message processing, aiding in analysis and troubleshooting.