> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Redis on Vortex IQ

> Monitor Redis health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Redis health, cost and reliability signals, and catch incidents and runaway spend early.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=redis)

<CardGroup cols={5}>
  <Card title="32">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="0">
    prepared fixes
  </Card>

  <Card title="0">
    proven workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (21 signals)">
        | Signal                                                 | Alert behaviour          | What it tracks                                                                                               |
        | ------------------------------------------------------ | ------------------------ | ------------------------------------------------------------------------------------------------------------ |
        | **Blocked Clients (BLPOP / BRPOP / WAIT)**             | Alert band 20 / 100      | Clients waiting on blocking commands , queue-consumer + pub/sub stacks live here.                            |
        | **Clients vs maxclients %**                            | Alert band 70 / 90       | connected\_clients / maxclients. Hitting cap rejects new connections , drops downstream services.            |
        | **Cluster Slot Coverage Gap (\<16384 slots assigned)** | Merchant rule            | Redis-distinctive , slot coverage gap = some keys unreachable, commands on those slots fail.                 |
        | **Cluster Slots Assigned (of 16384)**                  | Alert band 16384 / 16383 | cluster\_slots\_ok from CLUSTER INFO. \<16384 = some keys unreachable (operations on those slots fail).      |
        | **Connected Clients**                                  | Watch only               | Description pending editorial review; the signal is live.                                                    |
        | **Connected Replicas**                                 | Alert band 1 / 0         | connected\_slaves from INFO replication.                                                                     |
        | **Connections Rejected Due to maxclients**             | Alert band 70 / 90       | Alerts for Connections Rejected Due to maxclients.                                                           |
        | **Evicted Keys / minute**                              | Merchant rule            | evicted\_keys delta , Redis at maxmemory dropping keys per maxmemory-policy. Indicates memory pressure.      |
        | **Eviction Storm (>1k evicted\_keys/min sustained)**   | Merchant rule            | Alerts for Eviction Storm (>1k evicted\_keys/min sustained).                                                 |
        | **Expired Keys / minute**                              | Watch only               | Expired Keys / minute over time.                                                                             |
        | **Instance Uptime**                                    | Watch only               | Description pending editorial review; the signal is live.                                                    |
        | **Keyspace Hit Rate %**                                | Alert band 95 / 80       | keyspace\_hits / (keyspace\_hits + keyspace\_misses) from INFO stats. The Redis-defining metric.             |
        | **Last AOF Rewrite Status**                            | Alert band 1 / 0         | aof\_last\_bgrewrite\_status from INFO persistence (ok \| err).                                              |
        | **Last RDB Save (minutes ago)**                        | Alert band 30 / 60       | rdb\_last\_save\_time from INFO persistence.                                                                 |
        | **Last Successful Backup (hours ago)**                 | Alert band 24 / 72       | Last successful RDB / AOF backup shipped offsite. For ElastiCache: CloudWatch backup events.                 |
        | **Memory Fragmentation Ratio**                         | Merchant rule            | mem\_fragmentation\_ratio = used\_memory\_rss / used\_memory. >1.5 = OS waste; \<1 = swap in progress (BAD). |
        | **Memory Used vs Maxmemory %**                         | Alert band 70 / 90       | used\_memory / maxmemory , Redis treats memory as 'disk'. Approaching maxmemory triggers eviction.           |
        | **Operations per Second (live)**                       | Watch only               | instantaneous\_ops\_per\_sec from INFO stats. Redis-distinctive , proxy for command throughput.              |
        | **Redis Health Score**                                 | Alert band 80 / 70       | Description pending editorial review; the signal is live.                                                    |
        | **Replica Lag (seconds)**                              | Alert band 1 / 10        | master\_last\_io\_seconds\_ago from INFO replication on each replica.                                        |
        | **Total Keys (db0)**                                   | Watch only               | From INFO keyspace db0:keys=.                                                                                |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                       | Alert behaviour      | What it tracks                                                                                                                                            |
        | ---------------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Command Latency p50 (us)** | Watch only           | From LATENCY HISTORY (Redis 7+) or sampling client-side.                                                                                                  |
        | **Command Latency p95 (ms)** | Alert band 50 / 200  | Redis commands typically sub-ms; p95 >10ms = something pathological (large key, slow Lua script, swap).                                                   |
        | **Command Latency p99 (ms)** | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                                                                 |
        | **SLOWLOG Entries (15m)**    | Alert band 2 / 10    | Commands exceeding slowlog-log-slower-than threshold (default 10ms).                                                                                      |
        | **Slow-Query Rate %**        | Alert band 1 / 5     | SLOWLOG entry count in the trailing 15m divided by an estimated command count for that same window (INFO stats instantaneous\_ops\_per\_sec x 900s - Redi |
        | **Top 10 SLOWLOG Commands**  | Watch only           | Top 10 SLOWLOG Commands, broken down by row.                                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                  |
        | ------------------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------- |
        | **Connected Clients Saturation vs Traffic Burst** | Alert band 70 / 90 | Connected Clients Saturation vs Traffic Burst, broken down by row.                              |
        | **Redis OPS Spike vs Ecom Order Rate**            | Merchant rule      | Description pending editorial review; the signal is live.                                       |
        | **Redis Session Keys vs Active Ecom Users**       | Merchant rule      | Redis-distinctive: when Redis holds sessions, session-key count should track active ecom users. |
        | **Slow Commands During Checkout Window (5m)**     | Merchant rule      | Slow Commands During Checkout Window (5m), broken down by row.                                  |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                                 |
        | ------------------------------ | ------------------ | ------------------------------------------------------------------------------ |
        | **Rejected Connections (24h)** | Alert band 0.1 / 1 | rejected\_connections from INFO stats , clients refused due to maxclients hit. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### Audit risks and opportunities

    A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>
    </AccordionGroup>

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **0 write** operations across cluster infos, cluster nodes, info clients, info memorys, info persistences, info replications on Redis. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=redis)

    #### Ready to build your first Redis workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | cluster infos     | 1               | 0                |
      | cluster nodes     | 1               | 0                |
      | info clients      | 1               | 0                |
      | info memorys      | 1               | 0                |
      | info persistences | 1               | 0                |
      | info replications | 1               | 0                |
      | info servers      | 1               | 0                |
      | info stats        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>