-
Problem report
-
Resolution: Cannot Reproduce
-
Major
-
None
-
5.2.4
-
Sprint 74 (Mar 2021), Sprint 75 (Apr 2021), Sprint 76 (May 2021), Sprint 77 (Jun 2021), Sprint 78 (Jul 2021), Sprint 79 (Aug 2021), Sprint 80 (Sep 2021), Sprint 81 (Oct 2021), Sprint 82 (Nov 2021), Sprint 83 (Dec 2021), Sprint 84 (Jan 2022), Sprint 85 (Feb 2022), Sprint 86 (Mar 2022), Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022), Sprint 90 (Jul 2022), Sprint 91 (Aug 2022), Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023)
On the newer versions of the Solaris server the pavailable value should include the ZFS pool to give the actual memory available percentage
However the zabbix agent on the server is not showing the pavailable value as expected.
#:~> zabbix_get -s host.com -k 'agent.version' 4.0.16 #:~> zabbix_get -s host.com -k 'vm.memory.size[pavailable]' 6.083881
Where this is the actual available percentage value on the server
$ mdb=$(echo "::memstat" | sudo -u zabbix sudo mdb -k); zfs=$(echo "$mdb" | gawk -F "[ %]+" '/^ZFS/{print $4}') $ free=$(echo "$mdb" | gawk -F "[ %]+" '/^Free [^\(]/ \{print $4}'); echo "$zfs+$free" | bc 93.2
Below are some of the pointers why with Solaris 11 onwards we should include the memory consumption by ZFS pool in the pavailable value
https://community.oracle.com/tech/apps-infra/discussion/3867433/memory-management-between-zfs-and-applications-in-oracle-solaris-11-x-doc-id-1663862-1
https://www.oracle.com/webfolder/community/oracle_sun_technologies/4112665.html
https://support.oracle.com/knowledge/Sun%20Microsystems/1663862_1.html
