NoSQL Manager: MongoDB, Redis, Cassandra and DynamoDB

NoSQL Manager investigates slow, lagging or full MongoDB, Redis, Cassandra and DynamoDB datastores node by node, and does not delete or wipe your data to fix them.

REQUEST DEMO

READ THE DOCS

2501's NoSQL Manager specialty finds out why a MongoDB, Redis, Cassandra or DynamoDB datastore is slow, lagging or running out of room, then applies a safe fix within its scope or tells a person exactly what to do next.

An application starts timing out and the datastore behind it is the first suspect. It might be one replica falling behind, one shard carrying more than its share, a cache close to its memory limit or a table being throttled. Each platform shows it differently, and few teams know all four well.

What 2501 does

The NoSQL specialty takes these requests from your ticketing system. It covers MongoDB, replicated or sharded, Redis on its own, with automatic failover or in cluster mode, Cassandra and ScyllaDB, and DynamoDB tables. It investigates replication lag, uneven shards, memory pressure, failover health, down or overloaded nodes, slow queries, hot spots and throttling, and pins each problem to the node, shard or table at fault. Within scope it can stop a runaway query or run maintenance that a ticket names.

Scope map of 2501's NoSQL Manager: it investigates replicas and shards on MongoDB, memory and failover on Redis, nodes on Cassandra and ScyllaDB and tables on DynamoDB, stops runaway queries and runs maintenance a ticket names; failover needs approval, capacity problems are escalated for planning, and your data, indexes and structure are never deleted or changed.

You stay in control

You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
Data, structure and topology stay yours: it never deletes, empties or wipes data, never changes indexes, structure, how many copies are kept or how data is split, and never fails over without approval.
Access is the hard limit: for DynamoDB, give it read access and no right to delete tables. Destructive commands can be blacklisted outright.
On-prem, cloud or hybrid: 2501 runs wherever you do, from your own data centre to the cloud.

Frequently asked

Will it delete data to free up space? No. A capacity problem is escalated for planning, not solved by removing keys, documents or tables.

Why is DynamoDB throttling when total capacity looks fine? Usually because traffic is concentrated on a few keys. 2501 reports that as a data design problem rather than raising capacity to hide it.

Problems it handles

Each page is one kind of ticket, and how this specialty handles it within the limits you set.

Redis near its memory limit, filled by a few very large keys and keys that never expired, is diagnosed by 2501, which reports the cause with the evidence, deletes no data and leaves capacity to a person

Problem

Redis running out of memory

Flushing Redis or lifting its memory limit clears the alert and can lose data. How 2501 finds what is filling the memory, deletes nothing, and leaves capacity to you.

See how it is handled

NoSQL Manager: MongoDB, Redis, Cassandra and DynamoDB

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE