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]

Hi @Jedidiah Brightbill ,

My pleasure.

It depends how you configure your Hyland Diagnostics logging. 

For instance, if you have a Route configured to log to file within the Application Server web.config, you would want to adjust that value so the messages being written to file are not truncated.  

If you are sending all of your Hyland Diagnostics traffic from the Application Server to the Hyland Diagnostics Service and then using the Hyland Diagnostics Service to write to file, then you would want to enable it in the Application Server web.config and the Hyland Diagnostics Service .json file.

However, if you are logging to a SIEM (third party log aggregator like Splunk), then you want to adjust it in the Application Server so the messages sent to the SIEM are not truncated.

If you are logging interactively to the Hyland Diagnostics Console via the Hyland Diagnostics Service, you might need to adjust the setting in the Hyland Diagnostics Service .json so the messages in the Hyland Diagnostics Console are not truncated (I have not tested this out).

Hope this helps.

[Ryan_Wakefield]

@Adam Shane ,

I tried to apply the XML example you gave to the Hyland.FullText.Server.exe.config file (since that is where you setup the logging there), but the service couldn't start because I believe the configuration key was invalid. So do you have an updated one for the FTS server?

Thanks.

[Peter_Hanson]

I cannot find where to set this to make it work.  I am using FHIR and need the Trace tab to show the full length JSON POST message.  Shouldn't this be correct?  I get an error opening the config.  But also wondering it this is the correct spot and file.  

<Hyland.Logging>
<WindowsEventLogging sourcename="Hyland Application Server" />

<Hyland.Logging TruncateLogValues="4096">
<Routes>
<Route name="DiagnosticsConsole">
<add key="Http" value="http://localhost:8989" />
<!-- <add key="minimum-level" value="Trace" /> -->
</Route>
<Route name="ErrorEventLog">
<!-- Write errors to the Event Log using the source specified above -->
<add key="HylandLog" />
<add key="minimum-level" value="Error" />
</Route>

[AdamShaneHyland]

Hey @Pete Hanson ,

You have duplicate <Hyland.Logging /> keys.  You can only have one.

<Hyland.Logging>
<WindowsEventLogging sourcename="Hyland Application Server" />

<Hyland.Logging TruncateLogValues="4096">
<Routes>
...

It should look like this ...

<Hyland.Logging TruncateLogValues="4096">
<WindowsEventLogging sourcename="Hyland Application Server" />

<Routes>
...

Best wishes.

[Peter_Hanson]

Thanks Adam, this configuration will not open in WAMCON.  Do I need to correctly enable <!--HYLAND DIAGNOSTICS?

<!--HYLAND DIAGNOSTICS
Used for debugging on machines with Hyland.Logging installed
-->
<<Hyland.Logging TruncateLogValues="4096">
<WindowsEventLogging sourcename="Hyland Application Server" />
<Routes>
<Route name="DiagnosticsConsole">
<add key="Http" value="http://localhost:8989" />
<!-- <add key="minimum-level" value="Trace" /> -->
</Route>
<Route name="ErrorEventLog">
<!-- Write errors to the Event Log using the source specified above -->
<add key="HylandLog" />
<add key="minimum-level" value="Error" />
</Route>