EP3 Diagnostics truncates log messages, even in detail view

[Jedidiah_Brigh1]

I'm attempting to view the full SQL query being executed by a particular OnBase activity, and the query is being truncated by the Diagnostics Console, even when viewed via detail view. This happens when viewed in the console or logging to external file. I don't recall this happening in v18, but I also may not have been viewing a query that long. The character limit appears to be 2048.

Is there a workaround for this?

[AdamShaneHyland · Accepted solution]

Hi @Jedidiah Brightbill ,

While it might not be documented in the MRG, this is functioning to specification with 20.3.15.1000 and higher.  The default character limit is 2048 as you referenced.  To get around this limit, you can update the Hyland.Logging configuration key adding the TruncateLogValues attribute.

Here is an example for XML based applications (e.g. Web Server, Application Server, etc) which use the web.config 

<Hyland.Logging TruncateLogValues="4096">

Here is an example for JSON based application (e.g. Hyland Diagnostics, Hyland IDP, etc) 

"Hyland.Logging": {  "TruncateLogValues": "4096",  "Routes": {    "DiagnosticsConsole-Errors": {      "Http": "http://localhost:8989",      "minimum-level": "Verbose"    }  }}

You can set it to any value you would like, or set it to 0 which will disable the truncation.

Best wishes.

[Jedidiah_Brigh1]

Where is that configuration key set? DiagnosticsConsole.exe.config, web.config of the Diagnostics Service, web.config of app server, somewhere else? And also what parent block(s) it belongs in. The MRG doesn't have any information on it, unfortunately.

[AdamShaneHyland]

Hi @Jedidiah Brightbill ,

For web apps (i.e. Web Server, Application Server, etc), the <Hyland.Logging /> node is in the web.config.  For the any of the apps which use a JSON configuration for Hyland.Logging, the setting is a bit different.  I updated my original post so I could add the code block.

Best wishes.

[Jedidiah_Brigh1]

Thanks, that does help. The part I'm not clear on though is where in the pipeline this key applies, or how many applications are truncating values along the way where I will need to set the key. In other words, if any stage of the logging chain doesn't have an increased TruncateLogValues value, will that be the limiting point and it won't matter whether it's set to 0 upstream or downstream? That gate will truncate the log value to the default of 2048 if the key is unset.

For example, if I set the key to 0 for the Hyland Diagnostics service appsettings.json to disable truncation, but the Application Server is also truncating to 2048, will it not matter that it's uncapped in the Hyland Diagnostics service because log values are also being truncated at the App Server level, so I still won't get the full log?

Basically, if I want my Diagnostics Console (or log to file) to have full, un-truncated logs, what are all the applications where I need to set this key in order to override the default behavior across every logging source in OnBase for which I may need full log values? Web Server web.config, App Server web.config, Diagnostics Service appsettings.json are 3 I know of, but are there any other limiting config files elsewhere that I need to change? And if so, which applications / services now have this 2048 limit?