- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā05-21-2019 08:17 AM
Hi All,
In Discovery log i am getting below error.
" Payload length 5712574 exceeded limit of 5000000 ".
to fix this we needs to change "mid.discovery.max_payload_size" property value. But this Global parameter.
i cheeked in system properties, Discovery properties and MID server properties, but no use.
can some one help me, where can i found this property ?
Thanks in Advance
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā05-21-2019 08:39 AM
you can add that property .
name : mid.discovery.max_payload_size
type : string
value: -1
write sys_properties.list in application nav and create new one.
Screenshot:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā10-06-2020 08:10 AM
I am on a Paris instance and seeing this same error during VCenter scan with error message reported by ESX Hosts Storage probe.
Skipped sensor for VMWare - vCenter ESX Hosts Storage because of error in payload: Payload length 8679851 exceeded limit of 5000000
I set the mid.discovery.max_payload_size system property to -1 (in sys_properties.list per the instructions above). I noticed the SN docs state to set this in the probe parameters tab in the probe. I will do that next.
Update: After setting probe parameter, I am now getting a different error, also related to size:
Sensor error when processing VMWareProbe/a.b.c.d: Payload attachment exceeds the limit of 5242880 bytes set by system property com.glide.attachment.max_get_size. Will adjust this property now. After multiple attempts, I have been unable to get past this error. I even cleared the property (to remove the max limit), but nothing changed and I still get this error.
Appreciate any help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā10-11-2021 03:15 AM
I caught the same error.
There are SN KB about it: