> ## 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.

# Neo4j on Vortex IQ

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

Monitor Neo4j 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=neo4j)

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

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

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    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="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </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>
    </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 (21)">
    ### Monitor performance

    21 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 (9 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                                                          |
        | -------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **Bolt Connections In Use**                        | Watch only         | Active connections from dbms.listConnections().                                                                                         |
        | **Cluster Member Not FOLLOWER/LEADER or Lag >10s** | Alert band 0 / 1   | Alerts for Cluster Member Not FOLLOWER/LEADER or Lag >10s.                                                                              |
        | **Cluster Members (role + state)**                 | Watch only         | From dbms.cluster.overview() - address, role (LEADER / FOLLOWER / READ\_REPLICA), databases hosted.                                     |
        | **Cluster Replication Lag (seconds)**              | Alert band 1 / 10  | Max last-applied-tx lag of any FOLLOWER vs LEADER (dbms.cluster.overview()). Enterprise cluster only.                                   |
        | **Database Status (ONLINE / OFFLINE)**             | Merchant rule      | currentStatus from SHOW DATABASES - surfaces STORE\_COPYING / OFFLINE / STARTING states.                                                |
        | **Long-Running Transaction Holding Locks (>60s)**  | Merchant rule      | Alerts for Long-Running Transaction Holding Locks (>60s).                                                                               |
        | **Page Cache Hit Ratio %**                         | Alert band 95 / 80 | Neo4j-distinctive - page-cache hits / (hits + faults) from db.stats / metrics. \<95% = store no longer fits in page cache, IO climbing. |
        | **Page Cache Hit Ratio Below 95%**                 | Alert band 0 / 1   | Alerts for Page Cache Hit Ratio Below 95%.                                                                                              |
        | **Queries per Second (live)**                      | Watch only         | Transaction-committed rate delta from db.stats / metrics - graph query throughput.                                                      |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                               | Alert behaviour     | What it tracks                                                                                                                                |
        | ------------------------------------ | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Long-Running Transactions (>30s)** | Merchant rule       | Neo4j-distinctive - open transactions from SHOW TRANSACTIONS with elapsedTime >30s hold locks + heap. Runaway Cypher / un-terminated session. |
        | **Query Latency p95 (ms)**           | Alert band 50 / 200 | p95 elapsedTime across transactions sampled from SHOW TRANSACTIONS over the window.                                                           |
        | **Top 10 Slow Transactions**         | Watch only          | From SHOW TRANSACTIONS ordered by elapsedTime - currentQuery, database, owner (hashed), elapsed.                                              |
        | **Transaction Rollback Rate %**      | Alert band 0.1 / 1  | Rolled-back / committed transactions from db.stats counters. Spike = deadlocks, constraint violations, or app retry storms.                   |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                                       |
        | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
        | **Connection Pool Saturation %**         | Alert band 70 / 90 | Active bolt connections / configured bolt thread-pool max. Saturation = new sessions queue or time out.                              |
        | **Last Successful Snapshot (hours ago)** | Alert band 24 / 72 | Aura-managed only - newest snapshot from the Aura management API. Self-managed merchants run neo4j-admin backup out of band (gated). |
        | **Neo4j Health Score**                   | Merchant rule      | Composite: p95 latency healthy x error-free x cluster-healthy x page-cache-warm x pool-headroom.                                     |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                         | Alert behaviour | What it tracks                                                                                                                     |
        | ---------------------------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
        | **JVM Heap Usage %**                           | Merchant rule   | JVM heap used / committed from dbms.queryJmx('java.lang:type=Memory'). Sustained >85% = GC pressure, OOM risk.                     |
        | **Neo4j Query Spike vs Ecom Order Rate**       | Merchant rule   | Recommendation graphs get hammered by scrapers - QPS up while orders flat = bot traffic on the recommendation endpoint.            |
        | **Slow Graph Ops During Checkout Window (5m)** | Merchant rule   | Graph powering on-site recommendations stalls → checkout pages slow → conversion drops. Surfaces graph latency as revenue at risk. |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                     | Alert behaviour | What it tracks                                                                                                                                    |
        | -------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Leader Elections (24h)** | Merchant rule   | Neo4j-distinctive - repeated leader elections = primary flapping (network / GC pause / hardware). Requires storing the leader identity over time. |
        | **Store Size**             | Watch only      | Total store size in bytes. Trend matters more than absolute - sudden growth = bulk import or runaway write.                                       |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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="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 **8 read** and **1 write** operations across dbquerys, dbstats, dbmclusteroverview()s, dbmlistconnections()s, dbmqueryjmxs, instances on Neo4j. 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=neo4j)

    #### Ready to build your first Neo4j 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 |
      | --------------------- | --------------- | ---------------- |
      | dbquerys              | 0               | 1                |
      | dbstats               | 1               | 0                |
      | dbmclusteroverview()s | 1               | 0                |
      | dbmlistconnections()s | 1               | 0                |
      | dbmqueryjmxs          | 1               | 0                |
      | instances             | 1               | 0                |
      | show databases        | 1               | 0                |
      | show transactions     | 1               | 0                |

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