Introduction

Memcached is one of the most popular key-value databases. Memcached database serves as the intermediary “cache” between front-end (apps and APIs) and back-end (external databases). Unlike other key-value databases like Redis, Memcached is completely volatile, i.e. all data goes straight to memory. As a direct consequence of this, the entire database is emptied when you restart the Memcached service.

OpsRamp Memcached Adapter provides a comprehensive solution to monitor the health and performance of business-critical Memcached servers. This adapter allows IT administrators to identify and resolve problems with caching systems before they can have an adverse impact on the business.

OpsRamp Memcached Adapter supports the following three types of statistics:

  • Memcached traffic statistics – defines the list of metrics that are used in collecting statistics regarding the Memcached database traffic.
  • Memcached Items statistics – defines the list of metrics that are used in collecting statistics regarding items stored in Memcached database.
  • Memcached Slabs statistics – defines the list of metrics that are used in collecting statistics regarding the size and limits of each slab of Memcached database.

Adding Memcached adapter monitors

A Memcached adapter monitor is a collection of Memcached metrics defined by OpsRamp.

To create a template:

  1. Go to Setup > Monitoring > Monitors. The MONITORS screen appears.
  2. Click + Add.
    CREATE A MONITOR screen appears.
  3. Click Add Metric to add Memcached metrics to this monitor.
    The Metrics page with the list of available Memcached metrics is displayed.
  4. Select the required metrics and click + Add Metrics.
    The metrics are added to the monitor.
  5. From Configuration Parameters, edit the default values for the configuration parameters.
  6. Click Save.

Creating templates

A template is an instantiation of a monitor. A template is applied to devices.

Assigning template

Once the creation of template is done, you can assign the template to resources.

What to do next