Amazon Neptune is a fast, reliable, fully managed graph database service that makes it easy to build and run applications that work with highly connected datasets. The core of Amazon Neptune is a purpose-built, high-performance graph database engine optimized for storing billions of relationships and querying the graph with milliseconds latency.
Amazon Neptune has the following capabilities:
- Supports popular graph models Property Graph and W3C RDF, and their respective query languages Apache TinkerPop Gremlin and SPARQL.
- Powers graph use cases such as recommendation engines, fraud detection, knowledge graphs, drug discovery, and network security.
Use the AWS public cloud integration to discover and collect metrics against the AWS service.
Monitoring Neptune Using Amazon CloudWatch
To set up the AWS integration and discover the AWS service, go to AWS Integration Discovery Profile and select
Neptune DB Cluster or
Neptune DB Instance.
CloudTrail event support
- Not Supported (Neptune DB Cluster and Neptune DB Instance)
CloudWatch alarm support
- Supported (Neptune DB Cluster and Neptune DB Instance)
- Configurable in OpsRamp AWS Integration Discovery Profile.
|OpsRamp Metric||Metric Display Name||Unit||Aggregation Type|
Total amount of backup storage, in bytes, used to support from the Neptune DB clusters backup retention window.
For a read replica, amount of lag when replicating updates from the primary instance, in milliseconds.
Maximum amount of lag between the primary instance and each Neptune DB instance in the DB cluster, in milliseconds.
Minimum amount of lag between the primary instance and each Neptune DB instance in the DB cluster, in milliseconds.
Percentage of CPU utilization.
Amount of time that the instanceran, in seconds.
Amount of available random access memory, in bytes.
Number of requests per second to the Gremlin engine.
Number of open WebSocket connections to Neptune.
Number of loader requests per second.
Number of requests waiting in the input queue pending execution. Neptune starts throttling requests when they exceed Maximum queue capacity.
Incoming (receive) network traffic on the DB instance, including both customer database traffic and Neptune traffic used for monitoring and replication, in bytes/second.
Amount of network throughput both received from and transmitted to clients by each instance in the Neptune DB cluster, in bytes per second.
Outgoing (transmit) network traffic on the DB instance, including both customer database traffic and Neptune traffic used for monitoring and replication, in bytes/second.
Number of transactions successfully committed per second.
Number of transactions opened on the server per second.
Number of transactions per second rolled back on the server because of errors.
Total amount of backup storage consumed by all snapshots for a Neptune DB cluster outside its backup retention window, in bytes. Included in Total reported by TotalBackupStorageBilled metric.
Number of requests per second to the SPARQL engine.
Total amount of backup storage for which you are billed for a given Neptune DB cluster, in bytes. Includes the backup storage measured by the BackupRetentionPeriodStorageUsed and SnapshotStorageUsed metrics.
Total number of requests per second to the server from all sources.
Total number per second of requests that errored out because of client-side issues.
Total number per second of requests that errored out on the server because of internal failures.
Amount of storage used by your Neptune DB instance, in bytes. This value affects the cost of the Neptune DB cluster.
Average number of billed read I/O operations from a cluster volume, reported at 5-minute intervals.
Average number of write disk I/O operations to the cluster volume, reported at 5-minute intervals.