Generic Memory Usage (MPG1)

Description

Release notes

Show release notes
Version 1.1.0 - General deployment
  • Bugfix: Graphs generation code fixed. (M8461)
  • Improvement: Factorized common features from physical sops and virtual sops. (M8461)
  • Dependency:
    • SNMP Agent module v3.4.1 or higher
    • VSOP resource v1.0.5+

Resource configuration interface

GUI unavailable.

What is measured

This probe measures
  • for the physical SOPs: the memory usage in Megabytes. It also shows the swap usage in Megabytes.
  • for the vSOPs: the memory usage in Megabytes of the vsop and its processes. It also shows the swap usage in Megabytes of the same vsop and its process.

The two graphs are stacked one over the other. The memory usage is in the bottom of the overall graph and the swap is on top.

Resource parameters

  • Warning Level for the RAM
  • Critical Level for the RAM
  • Warning Level for the SWAP
  • Critical Level for the SWAP

Performance graphs

This probe generates a graph with following performance metrics:

  • RAM usage : the ram usage is in Megabytes.
  • RAM free : the ram usage is in Megabytes.
  • SWAP usage : the swap usage is in Megabytes.
  • SWAP free : the swap usage is in Megabytes.

Alarms

This probe can report following alarm states:

  • For the physical SOPs:
    • WARNING: When the memory usage surpassed the warning threshold for the RAM, the swap or both.
    • CRITICAL: When the memory usage surpassed the critical threshold for the RAM, the swap or both.

  • For the vSOPs:
    • WARNING: After 15 minutes during which the memory usage surpassed the warning threshold for the RAM, the swap or both.
    • CRITICAL: After 15 minutes during which the memory usage surpassed the critical threshold for the RAM, the swap or both.

Possible causes

The processes are requiring more memory space or the VSOP is not fast enough provoking caching of information.

Possible consequences

The host's performance might be affected and other VSOP on the same host might be affected also because the VSOP is taking all the CPU resources for itself.

Possible actions

  • Connect to the SOP Shell in order to identify which process is in cause:
    • SOP Shell > Diagnostics > System > CPU/Memory usage
    • Press Shift+m to order process by memory usage
  • If it is the Communication Server, restart it by:
    • SOP Shell > Diagnostics > Communication Server > Open Console Then type "restart now"
  • If it is the Database Server, restart it by:
    • SOP Shell > Subsystems > MySQL Server > Restart"
  • Contact Escaux

Additional notes

Requires SNMP agent to be installed on the VSOP itself.
Copyright © Escaux SA