I wouldn’t be surprised if other OS -related things are broken on Phantom OS as well. We use JNA for most native calls. Look at `git grep Native.register` to see what posix-like things might be affected.
Anthony > On Feb 6, 2019, at 7:28 AM, Jacob Barrett <[email protected]> wrote: > > We don’t have any hooks into the stats for this OS. > > On Feb 6, 2019, at 7:16 AM, Jens Deppe <[email protected] > <mailto:[email protected]>> wrote: > >> From SLES 11 to Phantom OS >> >> (I had already asked asked, but my CC got scrambled :( ) >> >> On Wed, Feb 6, 2019 at 7:10 AM Anthony Baker <[email protected] >> <mailto:[email protected]>> wrote: >> Which OS did you upgrade to? >> >> Anthony >> >>> On Feb 6, 2019, at 1:25 AM, Vahram Aharonyan <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi All, >>> >>> For our troubleshooting purposes we have been collecting some data from >>> Geode cluster members using following APIs: >>> >>> org.apache.geode.management.MemberMXBean#getFunctionExecutionRate >>> org.apache.geode.management.MemberMXBean#getPutsRate >>> org.apache.geode.management.MemberMXBean#getGetsRate >>> >>> org.apache.geode.management.NetworkMetrics#getBytesReceivedRate >>> org.apache.geode.management.NetworkMetrics#getBytesSentRate >>> >>> org.apache.geode.management.DiskMetrics#getDiskFlushAvgLatency >>> org.apache.geode.management.DiskMetrics#getDiskReadsRate >>> org.apache.geode.management.DiskMetrics#getDiskWritesRate >>> >>> Recently we have replaced our base OS and all the values reported back by >>> Geode during this calls become 0s. >>> Could someone help us to understand how these metrics are being collected >>> by Geode? Could it be that Geode uses some system utilities or system calls >>> that existed in our previous appliance and are removed in our newer version >>> of system causing Geode returning only 0s. >>> >>> Thanks, >>> Vahram. >>
