Skip to content

Latest commit

 

History

History
87 lines (59 loc) · 3.53 KB

memory.md

File metadata and controls

87 lines (59 loc) · 3.53 KB

memory

Monitor Type: memory (Source)

Accepts Endpoints: No

Multiple Instances Allowed: No

Overview

This monitor reports memory and memory utilization metrics.

On Linux hosts, this monitor relies on the /proc filesystem. If the underlying host's /proc file system is mounted somewhere other than /proc please specify the path using the top level configuration procPath.

procPath: /proc
monitors:
 - type: memory

Configuration

To activate this monitor in the Smart Agent, add the following to your agent config:

monitors:  # All monitor config goes under this key
 - type: memory
   ...  # Additional config

For a list of monitor options that are common to all monitors, see Common Configuration.

This monitor has no configuration options.

Metrics

These are the metrics available for this monitor. Metrics that are categorized as container/host (default) are in bold and italics in the list below.

  • memory.available (gauge)
    (Windows Only) Bytes of memory available for use.
  • memory.buffered (gauge)
    (Linux Only) Bytes of memory used for buffering I/O.
  • memory.cached (gauge)
    (Linux Only) Bytes of memory used for disk caching.
  • memory.free (gauge)
    (Linux Only) Bytes of memory available for use.
  • memory.slab_recl (gauge)
    (Linux Only) Bytes of memory, used for SLAB-allocation of kernel objects, that can be reclaimed.
  • memory.slab_unrecl (gauge)
    (Linux Only) Bytes of memory, used for SLAB-allocation of kernel objects, that can't be reclaimed.
  • memory.used (gauge)
    Bytes of memory in use by the system.
  • memory.utilization (gauge)
    Percent of memory in use on this host. This metric reports with plugin dimension set to "signalfx-metadata".

Non-default metrics (version 4.7.0+)

The following information applies to the agent version 4.7.0+ that has enableBuiltInFiltering: true set on the top level of the agent config.

To emit metrics that are not default, you can add those metrics in the generic monitor-level extraMetrics config option. Metrics that are derived from specific configuration options that do not appear in the above list of metrics do not need to be added to extraMetrics.

To see a list of metrics that will be emitted you can run agent-status monitors after configuring this monitor in a running agent instance.

Legacy non-default metrics (version < 4.7.0)

The following information only applies to agent version older than 4.7.0. If you have a newer agent and have set enableBuiltInFiltering: true at the top level of your agent config, see the section above. See upgrade instructions in Old-style whitelist filtering.

If you have a reference to the whitelist.json in your agent's top-level metricsToExclude config option, and you want to emit metrics that are not in that whitelist, then you need to add an item to the top-level metricsToInclude config option to override that whitelist (see Inclusion filtering. Or you can just copy the whitelist.json, modify it, and reference that in metricsToExclude.