Skip to main content

ElastiCache Hot Shard Debugger

Debug hot shard issues in AWS ElastiCache (Redis/Valkey) clusters with a beautiful web interface.

Quick Start

# Install
pip install elasticache-monitor

# Run
elasticache-monitor

Open http://localhost:8099 and start monitoring!


Features

  • 🌐 Web Interface — Modern UI with real-time updates
  • ⏱️ Live Monitoring — Countdown timer, per-shard status
  • 📊 Interactive Charts — Click to filter, right-click to hide
  • 🔍 Analysis — Sortable tables for keys, patterns, shards, commands
  • 🔄 Compare Jobs — Side-by-side comparison of 2-4 sessions
  • 💾 SQL Queries — Built-in editor with quick query templates

Usage

1. Start the Server

elasticache-monitor              # Default port 8099
elasticache-monitor --port 3000  # Custom port

2. Create a Monitoring Job

  1. Enter your Replication Group ID
  2. Enter your Redis/Valkey password
  3. Set duration (30-300 seconds)
  4. Click Start Monitoring

3. View Results

  • Dashboard — Real-time command counts, shard status
  • Charts — Command distribution, key patterns
  • Analysis — Deep dive into keys and patterns
  • Compare — Compare multiple monitoring sessions

Requirements

  • Python 3.12+
  • AWS credentials (for endpoint auto-discovery)
  • Network access to ElastiCache cluster

Install

# Using uv (recommended)
uv pip install -e .

# Or pip
pip install -e .

Production Safety

⚠️ Always use replica endpoints for monitoring in production. The MONITOR command can impact performance on primary nodes.

The web UI defaults to replica endpoints.


AWS Permissions

{
  "Effect": "Allow",
  "Action": [
    "elasticache:DescribeReplicationGroups",
    "elasticache:DescribeCacheClusters"
  ],
  "Resource": "*"
}

Documentation

Document Description
CLI Reference Command-line tools (for scripting)
Database Schema SQLite schema & example queries
Changelog Version history

CLI (Legacy)

For scripting and automation, CLI tools are still available:

elasticache-monitor-cli -c my-cluster -p PASSWORD -d 60

See docs/CLI.md for full reference.


Version: 2.0.0 · Python: 3.12+ · License: MIT

Metadata

Release files for elasticache-monitor 1.0.21

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for elasticache-monitor 1.0.21
File Size Uploaded Provenance Actions
elasticache_monitor-1.0.21.tar.gz 169.3 kB With provenance Details for elasticache_monitor-1.0.21.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for elasticache-monitor 1.0.21
File Interpreter ABI Platform Actions
elasticache_monitor-1.0.21-py3-none-any.whl Python 3 none any Details for elasticache_monitor-1.0.21-py3-none-any.whl

Total release size: 292.5 kB

Release files / elasticache_monitor-1.0.21.tar.gz

Download URL elasticache_monitor-1.0.21.tar.gz
Size 169.3 kB
Tags Source
SHA-256 checksum
How to use checksums
26da21cfb04bfdfea7c0be623f90606a6c4bd1a4c7fa9296d2d63ca76032b3e3
BLAKE2b-256 checksum
How to use checksums
4541a262ae5060f955b153b857098bc3320cbd8db7328b7c9f30826da6463bad
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 5, 2026.

Transparency log

Release files / elasticache_monitor-1.0.21-py3-none-any.whl

Download URL elasticache_monitor-1.0.21-py3-none-any.whl
Size 123.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
75b5628d254210b0c880afafa641ca4cab3de29d7b238e8f240646ac5cd0c49b
BLAKE2b-256 checksum
How to use checksums
04678bf8322ba32e70106992cbebb5316a795e9f8699b4fd9d38714ea7999634
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 5, 2026.

Transparency log

Security for elasticache-monitor 1.0.21

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for elasticache_monitor-1.0.21.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 5, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page