SN System Properties Reference
Property reference

mid.log.level

The mid.log.level property sets the logging level for the MID Server, allowing for different verbosity of log messages. Administrators should adjust this setting to debug for detailed logs during troubleshooting or to info for standard operational logging.

Default
Not stated
Type
Not stated
Application
Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do? It configures the logging level of the MID Server, with options including debug, info, warn, and error, affecting the detail of logs generated.
What area does it affect? MID Server logging
What does the default mean? No default value is stated in the ServiceNow documentation.
When should you review it? Review this property when troubleshooting issues or adjusting logging detail for performance monitoring.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name mid.log.level
Type Not stated
Application Not stated
Default value Not stated
Description Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context
Context preview Snippet 1
... names, and logos may be trademarks of the respective companies with which they are associated. 3620 Metric Intelligence performance can be checked in the MID Server log file when the mid.log.level MID Server parameter is in debug mode. Metric Intelligence performance numbers are available in the Performance Statistics [sa_performance_statistics] table. To view the performance numbers, filter the Performance Statistics list for ...
Brazil docs View supporting context
Context preview Snippet 2
... the details of the error message. MID Server logs To enable the detailed ECC firewall logging, increase the log level by setting the value of the MID Server configuration parameter, mid.log.level, to TRACE. The detailed logs provide information about: • Rules that the MID Server loaded from the boot configuration file. • Granular execution trace of rules. • Specific rule due ...
Brazil docs View supporting context
Context preview Snippet 3
... to true causes intensive logging on the MID Server, potentially using considerable disk space. • Type: true | false • Default value: false This parameter has been replaced by the mid.log.level parameter. debug [Deprecated] Specifies whether to enable debug logging on the MID Server. Normally this parameter is only used by developers, but it is occasionally useful when troubleshooting a problem. ...

More in mid

Other properties in the same namespace.

mid.jdbc.datastream.max.record.size This property limits the size of records processed by the MID Server's JDBC data stream, with a default maximu mid.keystore.max_backups This property determines how many key store backups can be retained, with a default limit of three backups. mid.local.run_on_startup This property configures the local MID server to run automatically at system startup, facilitating continuous mid.log.command_audit.enable This property enables logging of commands run by the MID Server, capturing details such as command names, hash mid.max_down_days It defines the threshold in days for how long a MID Server can remain down before it is treated as inactive fo mid.mi.anomaly_detection.disable This property, when set to true, prevents the system from detecting and reporting anomalies in CI metrics. mid.nmap.npcap.version This property defines the specific version of Npcap used during the installation of Nmap, impacting how Nmap o mid.nmap.safe.scripts This property defines which scripts are considered safe for use by Nmap, impacting the security and functional

All 59 properties in mid →