What is the purpose of the following ServiceNow system properties?

SakshamB
Tera Contributor

Monday

 

Hi Community,

Can someone please help explain the use and impact of the following ServiceNow system properties?

 

com.glide.cs.debug.topicblocklogging.enabled
sa.ie.log.service_cache_severity_level
sa.ie.log.ie_severity_level
com.glideapp.servicecatalog.log

 

Specifically, I’m looking to understand:

  • What each property is used for

  • Which module or functionality they relate to (e.g., Service Catalog, Integration Engine, etc.)

  • Whether they are meant for debugging/logging only

  • Any performance or security impact of disabling or changing them

  • Recommended values for production environments

I checked the documentation but couldn’t find clear explanations for these properties.

Thanks in advance for your help!

Labels:
0 Helpfuls
  • 97 Views
1 REPLY 1

vaishali231
Giga Guru

Monday

 

Hi @SakshamB 


I checked these properties directly on the instance and reviewed their descriptions and values. Below is a clarified explanation based on what they are actually used for.

 

sa.ie.log.ie_severity_level
This property controls the logging level for the Identification Engine (not generic Integration Engine).
It defines how much detail is written to logs when Identification Engine processes data such as CI identification, reconciliation, and service mapping activities.

Available values include Info, Warn, Error, Debug, DebugVerbose, and DebugObnoxious.
Setting it to Debug or higher produces very detailed logs and is mainly useful for troubleshooting Identification issues.

This is a logging-only property.
In production, it is recommended to keep this at Warn or Error. Debug levels should be enabled only temporarily, as they can generate large log volumes and impact performance.

 

sa.ie.log.service_cache_severity_level
This property controls logging for service cache operations used by the Identification Engine.
It helps troubleshoot cache behavior during CI identification and service mapping.

It is strictly for diagnostics and logging.
Lower severity levels increase log noise and can affect performance in environments with heavy Identification Engine usage.

Recommended setting in production is Warn or Error.

 

com.glideapp.servicecatalog.log
This property controls the log and trace level for Service Catalog processing, including catalog item execution and multi-catalog behavior.

The default value is notice.
Setting it to info or debug increases verbosity and is helpful when diagnosing catalog request failures or workflow issues.

This property is meant for troubleshooting only.
In production, it should remain at notice or warning, and debug should be used only for short-term investigation.

 

com.glide.cs.debug.topicblocklogging.enabled
This property controls debug logging for topic block validation introduced in the Vancouver release.
It is related to Customer Service and conversational logic where topics may be blocked or validated.

When enabled, it logs detailed topic block evaluation information.
This is purely for debugging and should not be left enabled in production, as it can increase log volume and impact performance.

Recommended value for production is false.

*************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.

Regards
Vaishali Singh

0 Helpfuls