vCenter Probes: processing error: payload attachment greater than 5MB

[srikanthnelapud]

Overview

Regarding the error - "Payload attachment exceeds the limit of 5242880 bytes set by system property com.glide.attachment.max_get_size". One of the customers recently asked me if anything can be done and this article is to help them because it contains the information gathered after some investigation is done and double-checking with the respective SMEs and architect owner(s).

Also, please note this article is more related to the VMWare as the error reported is with the vCenter probes and not guaranteed to align with other use cases.

Background

The property "com.glide.attachment.max_get_size" isn't available for the customer(s) OOTB in the "sys_properties" table and it is one of the Glide property itself to manage the input payload from various incoming sources or flows. By default, it is set to 5MB to avoid the system running into Out of Memory issue(s) so it's not at all recommended to change the size then as it might make the other products unstable because it's a kind of global property.

For vCenter

For the vCenter probes, for example- "VMWarevCenterESXHostsStorageProbe". We have a probe parameter called "page_size" and it is used to determine how many CIs data should be pulled in one request (1 ECC Queue Payload). By default, the value is "5" if there is no such parameter created then the payload is limited is max 5 CI's data.
SCREENSHOT:  SCREENSHOT -1.png

Out of the box, we don't any property shipped (SCREENSHOT -2.png) but the customer(s) can create it manually for the necessary probe(s) to avoid the page size issue. For example, (SCREENSHOT -3.png)

Possible Fix / Workaround

STEP-1: Go to the "Probes" under "Discovery Definition".
STEP-2: Search for the probe name that is causing the payload size issue(s).
STEP-3: In the below tabs - "Probe Parameters" section, add the parameter name whose name is "page_size"
STEP-4: Go to MID Server Script Include("ecc_agent_script_include") table
STEP-5: Open the script include whose name is according to the probe name (SCREENSHOT -1.png)
STEP-6: Search in the script with text as "parseInt(probe.getParameter('page_size'))" then you'll fine below code:
parseInt(probe.getParameter('page_size')) || <<SOME NUMBER>>
STEP-7: Copy the number which you saw in STEP-6 and now open the probe parameter created in STEP-3
STEP-8: Put the lesser number than the value of the probe parameter. (SCREENSHOT -3.png)