setPoolStatisticInterval does cause the client to send some of its stats periodically to the server. But the server puts this information into MBeans and does not write them to the server's statistic archive. This is why the javadoc's on setPoolStatisticInterval refers to "gfmon". Your best bet, as Dan and Anthony pointed out, is to have your client generate its own gfs file. You can do this be configuring the geode/gemfire properties as documented. You should find documentation about setting the following properties: statistic-sampling-enabled, statistic-sample-rate, statistic-archive-file, enable-time-statistics. One of the ways you can set these properties is using ClientCacheFactory.set(String, String)
On Tue, Apr 16, 2019 at 6:29 AM Alberto Bustamante Reyes <alberto.bustamante.re...@est.tech> wrote: > Hi Geode community, > > Im trying to run a simple test to check how the client stats are published > on the server, but I have not been able to do it. > > The server is started with the statistic sampling enabled, and in the > client I set the sending interval with setPoolStatisticInterval, but when I > open the stats file with VSD, I cannot see any "ClientStat" there. I was > expecting to see the stats "Client-to-Server Messaging Performance > (ClientStats)". > > I have checked the code and these two actions (setting time interval and > stats sampling) are the two conditions that enable the publishing of the > client stats, if Im not wrong. > > What am I missing? Thanks in advance. > > BR/ > > Alberto >
