Discovery - Pattern Log: Result is larger than 1000 characters and was truncated by the logger

[Carolyn Rast]

I was getting errors in the Pattern Log - setAttribute(ip_network_adapter_relation,........)
The max object size reached the maximum limit of [1000]. To adjust this use the mid property mid.sm.discolog.max_object_size.

I added a property to my MID server - mid.sm.discolog.max_object_size = 2000 - and restarted server.  I can see the change took effect in some entries:

The max object size reached the maximum limit of [20000]. To adjust this use the mid property mid.sm.discolog.max_object_size.

But in other entries I'm still seeing the 1000 character limit:

Result is larger than 1000 characters and was truncated by the logger

What did I miss?

[Alberto Consonn · Accepted solution]

Hi Carolyn,

as per Jim Zeigler feedback on the below thread, you should increase more the value of the system property mid.sm.discolog.max_object_size cause there might be some entries exceeding 2000 as well, please try to set the value to 100000 and make a new test:

https://community.servicenow.com/community?id=community_question&sys_id=b55a06c1dbd80c945129a851ca96...

If I have answered your question, please mark my response as correct and/or helpful.

Thank you very much

Cheers
Alberto

[Carolyn Rast]

Thank you Alberto.

I set mid.sm.discolog.max_object_size = 100000 - and restarted server.

The max object size errors are gone. 

The logger truncation message remains and many log entries are truncated (only one reports the truncation message).

[Alberto Consonn]

You could increase again the size value, however be aware this could impact your instance in terms of performance, so please share this risk with the business.

Cheers

Alberto

[Ashutosh Munot1]

Yeah. this will increase the pattern execution time. If you are ready to consume that time then go for it.

Thanks,
Ashutosh