Once you’ve integrated with AWS CloudWatch, you have access to all metrics for Amazon Neptune, a fully managed graph database service.
See all AWS integrations.
To verify metrics are reporting, search for the metrics in the Metric details page in Settings.
The following table shows the Neptune metrics ingested by Cloud Observability.
| Metric Name | Unit | Description |
|---|---|---|
| aws.neptune.backup_retention_period_storage_used | bytes | The total amount of backup storage utilized to support from the Neptune DB cluster's backup retention window. |
| aws.neptune.buffer_cache_hit_ratio | percent | The proportion of requests served by the buffer cache. |
| aws.neptune.cluster_replica_lag | milliseconds | The amount of lag experienced by a read replica when replicating updates from the primary instance. |
| aws.neptune.cluster_replica_lag_maximum | milliseconds | The maximum amount of lag between the primary instance and each Neptune DB instance in the DB cluster. |
| aws.neptune.cluster_replica_lag_minimum | milliseconds | The amount of lag between the primary instance and each Neptune DB instance in the DB cluster. |
| aws.neptune.cpu_utilization | percent | The percent of CPU utilization. |
| aws.neptune.engine_uptime | seconds | The amount of time that the instance has been running. |
| aws.neptune.freeable_memory | byte | The amount of available random access memory, in bytes. |
| aws.neptune.global_db_data_transfer_bytes | count | The number of bytes of redo log data transferred from the primary AWS Region to a secondary AWS Region in a Neptune global database. |
| aws.neptune.global_db_replicated_write_io | count | The number of write I/O operations replicated from the primary AWS Region in the global database to the cluster volume in a secondary AWS Region. |
| aws.neptune.global_db_progress_lag | milliseconds | The time that a secondary cluster is behind the primary cluster for both user transactions and system transactions. |
| aws.neptune.gremlin_requests_per_sec | count/second | The total number of requests per second to the Gremlin engine. |
| aws.neptune.gremlin_web_socket_open_connections | count | The number of open WebSocket connections to Neptune. |
| aws.neptune.loader_requests_per_sec | count/second | The total number of loader requests per second. |
| aws.neptune.main_request_queue_pending_requests | count | The number of requests waiting in the input queue pending execution. Neptune starts throttling requests when they exceed the maximum queue capacity. |
| aws.neptune.ncu_utilization | percent | The percentenage of neptune capacity units currently being used by a Neptune instance. |
| aws.neptune.network_throughput | bytes/second | In bytes per second, the amount of network throughput received from and transferred to customers by each instance in the Neptune DB cluster. This performance excludes network traffic between DB cluster instances and the cluster volume. |
| aws.neptune.network_transmit_throughput | bytes/second | In bytes per second, the amount of outbound network throughput transmitted to customers by each instance in the Neptune DB cluster. This performance excludes network traffic between DB cluster instances and the cluster volume. |
| aws.neptune.num_tx_committed | count | The number of transactions successfully committed per second. |
| aws.neptune.num_tx_opened | count | The number of transactions opened on the server per second. |
| aws.neptune.num_tx_rolled_back | count | The number of transactions per second rolled back on the server because of errors. |
| aws.neptune.open_cypher_requests_per_sec | count | The total number of requests per second (both HTTPS and Bolt) to the openCypher engine. |
| aws.neptune.open_cypher_bolt_open_connections | count | The number of Bolt connections open to Neptune. |
| aws.neptune.serverless_database_capacity | bytes | The average of all the ServerlessDatabaseCapacity values of the DB instances in the cluster. |
| aws.neptune.snapshot_storage_used | bytes | The total amount of backup storage consumed by all snapshots for a Neptune DB cluster outside its backup retention window, in bytes. |
| aws.neptune.sparql_requests_per_sec | count | The number of requests per second to the SPARQL engine. |
| aws.neptune.stats_num_statements_scanned | count | The total number of statements scanned for DFE statistics since server start. |
| aws.neptune.total_backup_storage_billed | bytes | The entire amount of backup storage for a specific Neptune DB cluster for which you are invoiced, in bytes. Backup storage is represented by the BackupRetentionPeriodStorageUsed and SnapshotStorageUsed metrics. |
| aws.neptune.total_requests_per_sec | count | The total number of requests per second to the server from all sources. |
| aws.neptune.total_client_errors_per_sec | count | The total number per second of requests that errored out because of client-side issues. |
| aws.neptune.total_server_errors_per_sec | count | The total number per second of requests that errored out on the server because of internal failures. |
| aws.neptune.volume_bytes_used | bytes | The total amount of storage allocated to your Neptune DB cluster. |
| aws.neptune.volume_read_io_ps | count | Averaged number of billed read I/O operations from a cluster volume per 5-minute intervals. |
| aws.neptune.volume_write_io_ps | count | The average number of write disk I/O operations to the cluster volume per 5-minute intervals. |
| aws.neptune.gremlin_http_100 | count/second | The total number of HTTP 1xx responses for the Gremlin endpoint per second. |
| aws.neptune.gremlin_http_200 | count/second | The total number of HTTP 2xx responses for the Gremlin endpoint per second. |
| aws.neptune.gremlin_http_400 | count/second | The total number of HTTP 4xx errors for the Gremlin endpoint per second. |
| aws.neptune.gremlin_http_500 | count | The total number of HTTP 5xx errors for the Gremlin endpoint per second. |
| aws.neptune.gremlin_errors | count | The total number of errors in Gremlin traversals. |
| aws.neptune.gremlin_requests | count | The total number of requests to Gremlin engine. |
| aws.neptune.gremlin_web_socket_success | count/second | The total number of successful WebSocket connections to the Gremlin endpoint per second. |
| aws.neptune.gremlin_web_socket_client_errors | count | The total number of WebSocket client errors on the Gremlin endpoint per second. |
| aws.neptune.gremlin_web_socket_server_errors | count | The total number of WebSocket server errors on the Gremlin endpoint per second. |
| aws.neptune.gremlin_web_socket_available_connections | count | The total number of potential WebSocket connections currently available. |
| aws.neptune.http_100 | count | The total number of HTTP 100 responses for the endpoint per second. We suggest that you use the new HTTP 1xx combined metric instead. |
| aws.neptune.http_101 | count | The total number of HTTP 101 responses for the endpoint per second. We suggest that you use the new HTTP 1xx combined metric instead. |
| aws.neptune.http_1_xx | count | The total number of HTTP 1xx responses for the endpoint per second. |
| aws.neptune.http_200 | count | The total number of HTTP 200 responses for the endpoint per second. We suggest that you use the new HTTP 2xx combined metric instead. |
| aws.neptune.http_2xx | count | The total number of HTTP 2xx responses for the endpoint per second. |
| aws.neptune.http_400 | count | The total number of HTTP 400 errors for the endpoint per second. We suggest that you use the new HTTP 4xx combined metric instead. |
| aws.neptune.http_403 | count | The total number of HTTP 403 errors for the endpoint per second. We suggest that you use the new HTTP 4xx combined metric instead. |
| aws.neptune.http_405 | count | The total number of HTTP 405 errors for the endpoint per second. We suggest that you use the new HTTP 4xx combined metric instead. |
| aws.neptune.http_413 | count | The total number of HTTP 413 errors for the endpoint per second. We suggest that you use the new HTTP 4xx combined metric instead. |
| aws.neptune.http_429 | count | The total number of HTTP 429 errors for the endpoint per second. We suggest that you use the new HTTP 4xx combined metric instead. |
| aws.neptune.http_4xx | count | The total number of HTTP 4xx errors for the endpoint per second. |
| aws.neptune.http_500 | count/second | The total number of HTTP 500 errors for the endpoint per second. We suggest that you use the new HTTP 5xx combined metric instead. |
| aws.neptune.http_501 | count/second | The total number of HTTP 501 errors for the endpoint per second. We suggest that you use the new HTTP 5xx combined metric instead. |
| aws.neptune.http_5xx | count | The total The total number of HTTP 5xx errors for the endpoint per second. |
| aws.neptune.loader_errors | count | The total number of errors from Loader requests. |
| aws.neptune.loader_requests | count | The total number of Loader Requests. |
| aws.neptune.sparql_http_1xx | count/second | Per second, the number of HTTP 1xx replies for the SPARQL endpoint. Instead, we propose that you use the new HTTP 1xx combined metric. |
| aws.neptune.sparql_http_2xx | count/second | Per second, the number of HTTP 2xx replies for the SPARQL endpoint. Instead, we propose that you use the new HTTP 2xx combined metric. |
| aws.neptune.sparql_http_4xx | count/second | Per second, the number of HTTP 4xx failures for the SPARQL endpoint. Instead, we propose that you use the new HTTP 4xx combined metric. |
| aws.neptune.sparql_http_5xx | count/second | Per second, the number of HTTP 5xx failures for the SPARQL endpoint. Instead, we propose that you use the new HTTP 5xx combined metric. |
| aws.neptune.sparql_errors | count/second | The number of failures in SPARQL queries. |
| aws.neptune.sparql_requests | count | The number of SPARQL engine requests. |
| aws.neptune.status_errors | count | The total number of errors from the status endpoint. |
| aws.neptune.status_requests | count | The total number of queries made to the status endpoint. |
See also
Updated Dec 20, 2022