Skip Navigation
Show nav
Heroku Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
View categories

Categories

  • Heroku Architecture
    • Dynos (app containers)
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Command Line
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery
    • Continuous Integration
  • Language Support
    • Node.js
    • Ruby
      • Working with Bundler
      • Rails Support
    • Python
      • Background Jobs in Python
      • Working with Django
    • Java
      • Working with Maven
      • Java Database Operations
      • Working with Spring Boot
      • Java Advanced Topics
    • PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
    • Heroku Data For Redis
    • Apache Kafka on Heroku
    • Other Data Stores
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
    • Compliance
  • Heroku Enterprise
    • Private Spaces
      • Infrastructure Networking
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
    • Single Sign-on (SSO)
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
  • Add-ons
  • All Add-ons
  • Memetria Monitoring for Redis®*
Memetria Monitoring for Redis®*

This add-on is operated by Stovepipe Studios, Inc.

Track your Redis server's health and prevent problems before they occur.

Memetria Monitoring for Redis®*

Last updated August 29, 2022

Table of Contents

  • Compatibility
  • Provisioning the Add-on
  • Enabling Memory Monitoring
  • Viewing the Memetria dashboard
  • Updating your Redis URL
  • Rotating Credentials
  • Removing the Add-on
  • Additional Help

Memetria Monitoring for Redis is a monitoring package to track the health and performance of your Redis server. Memetria Monitoring for Redis makes it easy to save memory (and money) by exposing large keys, memory leaks, and unused keys.

It provides:

  • An interactive map of Redis memory usage
  • Large key identification and tracking
  • Continuous analysis of dozens of Redis-specific metrics

Compatibility

Memetria Monitoring for Redis works with all popular Redis add-on services and requires no additional code or configuration in your app.

Provisioning the Add-on

Add Memetria Monitoring for Redis to an app via the Heroku CLI. You can specify the URL of the Redis database to monitor using the “–url” flag:

$ heroku addons:create redismonitor:free --url redis://x:password@my.redis.host.com:11001/

If you don’t know your Redis URL, you can still add Memetria Monitoring for Redis to your app. You will be prompted to enter it when you open the Memetria dashboard.

$ heroku addons:create redismonitor:free

Enabling Memory Monitoring

Memetria Monitoring for Redis’s memory analysis features require a paid plan. You can upgrade to a paid plan using the CLI:

$ heroku addons:upgrade redismonitor:monitor0
Changing redismonitor-shaped-48055 on calm-beach-06843 from redismonitor:free to redismonitor:monitor0... done, ($7/mo)

The plan size required depends on the total number of keys in the Redis database that you monitor. After using Memetria Monitoring to reduce your memory usage, you can downgrade to a smaller plan:

$ heroku addons:downgrade redismonitor:monitor0
Changing redismonitor-shaped-48055 on calm-beach-06843 from redismonitor:monitor3 to redismonitor:monitor0... done, ($7/mo)

Heroku Data for Redis

$ heroku addons:create redismonitor:free --url `heroku config:get REDIS_URL`

Private Spaces

Heroku Private Spaces do not allow external connections for data services by default, but they can be enabled using Trusted IP ranges for data services. You can find the list of IP addresses that Memetria Monitoring for Redis uses to connect to your Redis server in Memetria’s documentation. When using CIDR notation to specify the IP addresses, you can use a mask of /32 for each IP address, e.g. 52.4.225.198/32, to ensure only Memetria’s IP addresses are used.

OpenRedis

$ heroku addons:create redismonitor:free --url `heroku config:get OPENREDIS_URL`

Redis Cloud

$ heroku addons:create redismonitor:free --url `heroku config:get REDISCLOUD_URL`

Viewing the Memetria dashboard

To access your Memetria dashboard, click on the Memetria Monitoring for Redis link on your app’s Heroku Dashboard page. You will be automatically redirected and logged in to your Memetria dashboard.

Updating your Redis URL

Your monitor’s Redis URL can be changed by clicking the “Settings” button on your Memetria dashboard. You will not lose any graph data — Memetria will begin graphing the new values in your existing graphs.

Rotating Credentials

See “Updating your Redis URL” above.

Removing the Add-on

After you remove Memetria Monitoring for Redis from your app, your Redis server will no longer be monitored and your graph data will be erased.

You can remove Memetria Monitoring for Redis from your app via the Heroku CLI:

$ heroku addons:destroy redismonitor
  !    WARNING: Destructive Action
  !    This command will affect the app: example-app
  !    To proceed, type "example-app" or re-run this command with --confirm example-app
  > example-app
 Removing redismonitor:free from example-app... done, v25 ($free)

Additional Help

Click the “Support” button in the Memetria dashboard or email us at support@memetria.com if you need any help with Memetria Monitoring for Redis.

Keep reading

  • All Add-ons

Feedback

Log in to submit feedback.

Ziggeo Mezmo

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Podcasts
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing

Subscribe to our monthly newsletter

Your email address:

  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Heroku Podcasts
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Facebook
  • Instagram
  • Github
  • LinkedIn
  • YouTube
Heroku is acompany

 © Salesforce.com

  • heroku.com
  • Terms of Service
  • Privacy
  • Cookies
  • Cookie Preferences