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?

[rajeshraya]

I created the system property mid.sm.discolog.max_object_size (first at global level) and later on the MID Server(s) level. I still face the error: "Result is larger than 1000 characters and was truncated by the logger" after rerunning the service map discovery.

Can you please suggest?

[Carolyn Rast]

Thank you Alberto.

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

The max object size errors are gone.

The 1000 character limit error remains:

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

Many entries are truncated but only one returns the 'truncated by the logger' message. for example:

2020-09-25 07:47:41: setAttribute(ArpTable,[{mac_address=00-00-0c-07-ac-a6, ip_address=10.100.166.1}, {mac_address=3c-08-f6-d5-ca-c7, ip_address=10.100.166.3}, {mac_address=00-50-56-8b-a9-c3, ip_address=10.100.166.16}, {mac_address=00-50-56-8b-2a-dc, ip_address=10.100.166.21}, {mac_address=00-50-56-8b-04-f3, ip_address=10.100.166.22}, {mac_address=00-50-56-8b-83-d3, ip_address=10.100.166.23}, {mac_address=00-50-56-8b-27-c5, ip_address=10.100.166.24}, {mac_address=00-50-56-8b-d9-9a, ip_address=10.100.166.25}, {mac_address=00-50-56-aa-56-a7, ip_address=10.100.166.27}, {mac_address=00-50-56-8b-9b-31, ip_address=10.100.166.28}, {mac_address=00-50-56-8b-e6-d4, ip_address=10.100.166.29}, {mac_address=00-50-56-aa-56-99, ip_address=10.100.166.36}, {mac_address=00-50-56-aa-75-c5, ip_address=10.100.166.37}, {mac_address=00-50-56-aa-15-78, ip_address=10.100.166.43}, {mac_address=00-50-56-a0-99-9d, ip_address=10.100.166.44}, {mac_address=00-50-56-aa-15-7f, ip_address=10.100.166.45}, {mac_address=00-50-56-a0-0c-b9, ip_

or

2020-09-25 07:47:38: setAttribute(cmdb_serial_number,[{SoftwareElementID=PhoenixBIOS 4.0 Release 6.0, internal_namespace=root/cimv2, serial_number=VMware-42 0b e2 8f cf 6d 39 39-30 39 7a e0 60 03 b8 87, SoftwareElementState=3, Name=PhoenixBIOS 4.0 Release 6.0, internal_classname=Win32_BIOS, OBJECT_REFERENCE=null, SerialNumber=VMware-42 0b e2 8f cf 6d 39 39-30 39 7a e0 60 03 b8 87, Version=INTEL - 6040000, SMBIOSBIOSVersion=6.00, __CLASS=Win32_BIOS, row_number=1, serial_number_type=bios, TargetOperatingSystem=0}, {SoftwareElementID=PhoenixBIOS 4.0 Release 6.0, internal_namespace=root/cimv2, serial_number=VMware-42 0b e2 8f cf 6d 39 39-30 39 7a e0 60 03 b8 87, SoftwareElementState=3, Name=PhoenixBIOS 4.0 Release 6.0, internal_classname=Win32_BIOS, OBJECT_REFERENCE=null, SerialNumber=VMware-42 0b e2 8f cf 6d 39 39-30 39 7a e0 60 03 b8 87, Version=INTEL - 6040000, SMBIOSBIOSVersion=6.00, __CLASS=Win32_BIOS, row_number=1, serial_number_type=bios, TargetOperatingSystem=0}, {internal_classname=Win32_ComputerSys

[Navneet Kaur2]

You can try changing the size of 'mid.sm.discolog.max_log_size'. Hope this will work.

Limits the length of the log statements in the Horizontal Discovery Log. If the results are truncated, the Command results reports, "Result is larger than [value] characters and was truncated by the logger."

• Type: integer (characters)
• Default value: 1000

[Jugmaz]

This is old topic, but I'd like to bump this a bit as it seems to be still topical.

If you are working with AWS discovery, credential-less and automated in AWS side with AssumeRole and trusted entities, you need to also add this property with value of 1000 - which leads to fact that payload is fit and all information related to service account or data center discovery is complete!

we had to spend days and days to find this out!