Neo4j

Neo4j

Agent Check Agent Check

Linux Mac OS Windows OS Supported

Overview

Get metrics from Neo4j service in real time to:

  • Visualize and monitor Neo4j states.
  • Be notified about Neo4j failovers and events.

Setup

The Neo4j check is not included in the Datadog Agent package, so you need to install it.

Installation

For Agent v7.21+ / v6.21+, follow the instructions below to install the Neo4j check on your host. See Use Community Integrations to install with the Docker Agent or earlier versions of the Agent.

  1. Run the following command to install the Agent integration:

    datadog-agent integration install -t datadog-neo4j==<INTEGRATION_VERSION>
    
  2. Configure your integration similar to core integrations.

Configuration

  1. Edit the neo4j.d/conf.yaml file in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your Neo4j metrics. See the sample neo4j.d/conf.yaml for all available configuration options.

  2. Restart the Agent

Validation

Run the Agent’s status subcommand and look for neo4j under the Checks section.

Data Collected

Metrics

neo4j.arraystore.size
(gauge)
The size of the array store
Shown as unit
neo4j.bytes.read
(gauge)
The total number of bytes read
Shown as unit
neo4j.bytes.written
(gauge)
The total number of bytes written
Shown as unit
neo4j.dbms.memory.pagecache.size
(gauge)
Memory Pagecache Size
Shown as unit
neo4j.page.cache.evictionexceptions
(gauge)
The total number of eviction exceptions
Shown as unit
neo4j.page.cache.evictions
(gauge)
The total number of page evictions executed by the page cache.
Shown as unit
neo4j.page.cache.faults
(gauge)
The total number of faults.
Shown as unit
neo4j.page.cache.filemappings
(gauge)
The total number of file mappings.
Shown as unit
neo4j.page.cache.fileunmappings
(gauge)
The total number of file unmappings.
Shown as unit
neo4j.page.cache.flushes
(gauge)
The total number of flushes executed by the page cache.
Shown as unit
neo4j.ha.pull_interval
(gauge)
The HA Pull Time Interval
Shown as unit
neo4j.kernel.starttime
(gauge)
Time when the kernel started
Shown as second
neo4j.kernel.version
(gauge)
The kernel version
Shown as unit
neo4j.last.committed.transaction.id
(gauge)
The last committed transaction id.
Shown as unit
neo4j.locks
(gauge)
The total number of locks.
Shown as unit
neo4j.logicallog.size
(gauge)
The logical log size setting.
Shown as unit
neo4j.memorypools
(gauge)
The size of memory pools.
Shown as unit
neo4j.node.store.size
(gauge)
The size of the node store.
Shown as unit
neo4j.averteddeadlocks
(gauge)
The total number of averted deadlocks.
Shown as unit
neo4j.committedtransactions
(gauge)
The total number of committed transactions.
Shown as unit
neo4j.nodeidsinuse
(gauge)
The total number of node ids in use.
Shown as unit
neo4j.opened.transactions
(gauge)
The total number of opened transactions.
Shown as unit
neo4j.open.transactions
(gauge)
The total number of open transactions.
Shown as unit
neo4j.property.ids.inuse
(gauge)
The total number of property ids in use.
Shown as unit
neo4j.relationship.ids.inuse
(gauge)
The total number of relationship ids in use.
Shown as unit
neo4j.relationshiptype.ids.inuse
(gauge)
The total number of relationship type ides in use.
Shown as unit
neo4j.peak.rolledback.transactions
(gauge)
The total number of rolled back transactions.
Shown as unit
neo4j.peak.concurrenttransactions
(gauge)
The peak number of concurrent transactions.
Shown as unit
neo4j.pins
(gauge)
The total number of page pins executed by the page cache.
Shown as unit
neo4j.property.store.size
(gauge)
The property store size.
Shown as unit
neo4j.relationship.store.size
(gauge)
The relationship store size.
Shown as unit
neo4j.store.creationdate
(gauge)
The store creation date.
Shown as unit
neo4j.storeid
(gauge)
The store id.
Shown as unit
neo4j.store.log.version
(gauge)
The store log version.
Shown as unit
neo4j.string.store.size
(gauge)
The string store size.
Shown as unit
neo4j.total.store.size
(gauge)
The total store size.
Shown as unit

Events

The Neo4j check does not include any events.

Service Checks

neo4j.can_connect
Returns CRITICAL if the Agent fails to receive a 200 status from the monitoring endpoint, otherwise returns OK.
Statuses: ok, critical

Troubleshooting

Need help? Contact Datadog support.