FAQ Entry
Register
* You must register for access to some support pages



Entry #193: What's the problem with MEGA conversion in collector.conf?

Question
What's the problem with MEGA conversion in collector.conf?
Answer
In the user guide, it describes an option, MEGA, which can be used to convert a value into megabytes. When applied as follows, the value always reports 0 (zero):

VARIABLE U_INT { VMem } = { VMem } MEGA;

Measurements, if not converted into MB by the collector, are considered illegal (too high) by the client and are displayed as zero.

The documentation is incorrect, but there is a way around this. To get the variables in MEG, follow these steps:

1. Change the line in collector.conf

from
VARIABLE U_INT { VMem } = { VMem } MEGA;

to
VARIABLE U_INT { VMem } = { VMem };

2. Edit the vpcom.conf file, and add the following (remember not to take the line literally, you have to have the syntax correct):

GROUP "Workloads"
ARRAY NAME = {Workloads.Name}
.
.
.
VARIABLE {VMemk} = {Workloads.Vmem, uint32, mbytes}
^
END ARRAY "
END GROUP "

This is what shows up on the PC. You can change it to "m" or "g" or whatever you want.