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
      • Working with Django
      • Background Jobs in Python
    • Java
      • Working with Maven
      • Java Database Operations
      • Working with the Play Framework
      • Working with Spring Boot
      • Java Advanced Topics
    • PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
    • Heroku 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)
    • 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
  • Databases & Data Management
  • Heroku Redis
  • Understanding Heroku Redis Log Statements and Common Errors

Understanding Heroku Redis Log Statements and Common Errors

English — 日本語に切り替える

Last updated January 25, 2021

Table of Contents

  • SLAVE OF …
  • CONFIG REWRITE
  • Database memory close to the limit

Heroku Redis logs to the logplex which collates and publishes your application’s log-stream. You can isolate Heroku Redis events with the heroku logs command by filtering for the redis process.

Logs are a premium-tier feature. They are not available on hobby-tier databases.

$ heroku logs -p redis -t

Besides seeing system-level Redis activity, these logs are also useful for understanding your application’s use of Redis and for diagnosing common errors. This article lists common log statements, their purpose, and any action that should be taken.

SLAVE OF …

2015-08-18T17:29:39Z app[redis]: [maturing-daily-1187] * SLAVE OF would result into synchronization with the master we are already connected with. No operation performed.

This indicates that Heroku Redis is ensuring your HA standby is following your primary Redis instances.

CONFIG REWRITE

2015-08-18T17:29:39Z app[redis]: [maturing-daily-1187] # CONFIG REWRITE executed with success.

This indicates that Heroku Redis has proceed to rewrite your Redis instance configuration, this happens whenever we need to change your instance configuration or when you trigger a configuration change.

Database memory close to the limit

2016-09-12T07:27:33+00:00 app[heroku-redis]: source=REDIS_URL sample#used_memory_over_limit=10435336.0bytes message=Database memory close to the limit. Please upgrade your database plan or change your maxmemory policy.

This log is seen when a Redis instance is using more than 90% of its plan memory limit. Since you can see this log before you actually exceed the limit, you can monitor this log to make an alert.

Keep reading

  • Heroku Redis

Feedback

Log in to submit feedback.

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