Ad Widget

Collapse

Zabbix incorrectly reporting vm.memory.size[pused]

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mbadmin
    Junior Member
    • Jan 2018
    • 22

    #1

    Zabbix incorrectly reporting vm.memory.size[pused]

    I'm trying to figure out why my server shows that I am using 90%+ of available memory.

    I have an item setup to report on vm.memory.size[pused] and the graph is writing data, I just don't believe it to be correct. My system I noticed this on has 48GB total memory.

    Here's the actual output of free -g :


    total used free shared buff/cache available
    Mem: 46 22 2 2 21 19
    Swap: 3 0 3





    I went to the docs and see that pused is defined as:
    pused - active + wired memory as percentage of 'total'

    So I decided to create 3 more items... vm.memory.size[active] and vm.memory.size[wired] and vm.memory.size[total] (this one already exists) to try and troubleshoot.

    The only one that actually shows me any data at all is vm.memory.size[total], the other two parameters of "wired" and "active" don't appear to return any data.

    -mb

  • dimir
    Zabbix developer
    • Apr 2011
    • 1080

    #2
    The page that you refer to has indeed explanation of metrics to get memory usage. But this page explains which parameters are supported on which platform:

    - active: FreeBSD, OpenBSD, NetBSD, Mac OS X, HP-UX
    - wired: FreeBSD, OpenBSD, NetBSD, Mac OS X

    I assume you are trying this on Linux. At the bottom of the page you refer to there is another link to more detailed explanation about the metric parameters.

    Comment

    • mbadmin
      Junior Member
      • Jan 2018
      • 22

      #3
      Thanks, that definitely explains why the wired and active don't work. Does this mean by extension that the pused wont be correct?

      Comment

      • dimir
        Zabbix developer
        • Apr 2011
        • 1080

        #4
        Not at all. It should be correct.

        Comment

        Working...