Amazon Neptune Instance Monitoring Integration
Amazon Neptune is a fully-managed graph database service used to build and run applications that work with highly connected datasets.
Setup and configuration
1. If you haven't already, enable access to your AWS resources between your AWS account and Site24x7's AWS account by either:
- Creating Site24x7 as an IAM user
- Creating a cross-account IAM role. Learn more
2. On the Integrate AWS Account page, check the box next to Amazon Neptune Instance. Learn more
Policies and permissions
The following permissions are required by Site24x7 to discover an Amazon Neptune Instance and collect configuration information. Learn more
- "rds:DescribeDBInstances",
- "rds:ListTagsForResource",
- "rds:DescribeDBClusters",
- "rds:DescribeEvents",
- "logs:DescribeLogStreams",
- "logs:GetLogEvents",
- "rds:DescribeDBClusterParameterGroups"
Polling Frequency
Site24x7 queries AWS to collect Neptune Instance performance metrics according to the configured poll frequency. The minimum poll interval supported is one minute, and the maximum is 24 hours. Learn more
IT Automations
You can add automations for the AWS services supported by Site24x7. Log in to Site24x7 and go to Admin > IT Automation Templates (+) > Add Automation Templates. Once automations are added, you can schedule them to be executed one after the other.
You can now reboot a Neptune instance using Amazon Neptune instance automations.
Supported metrics
Attribute | Description | Statistic | Data Type |
---|---|---|---|
Cluster ReplicaLag Maximum | The maximum amount of lag between the primary instance and each Neptune DB instance in the DB cluster | Maximum | Milliseconds |
Cluster ReplicaLag Minimum | The minimum amount of lag between the primary instance and each Neptune DB instance in the DB cluster | Minimum | Milliseconds |
Engine Up Time | The amount of time that the instance has been running | Maximum | Seconds |
Freeable Memory | The amount of random access memory available | Minimum | MB |
Free Local Storage | The amount of storage available for temporary tables and logs | Minimum | MB |
Gremlin Errors | The number of errors in Gremlin traversals | Sum | Count |
Gremlin Requests | The number of requests to the Gremlin engine | Sum | Count |
Gremlin Requests Per Sec | The number of requests to the Gremlin engine per second | Sum | Count/sec |
Gremlin WebSocket Available Connections | The number of potential WebSocket connections currently available | Sum | Count/sec |
Gremlin WebSocket Client Errors | The number of WebSocket client errors on the Gremlin endpoint per second | Sum | Count/sec |
Gremlin WebSocket Server Errors | The number of WebSocket server errors on the Gremlin endpoint per second | Sum | Count/sec |
Gremlin WebSocket Success | The number of successful WebSocket connections to the Gremlin endpoint per second | Sum | Count/sec |
Loader Errors | The number of errors from Loader requests | Sum | Count |
Loader Requests | The number of Loader Requests | Sum | Count |
Network Receive Throughput | The incoming network traffic on the DB instance, including both customer database traffic and Neptune traffic used for monitoring and replication | Average | MB/sec |
Network Throughput | The amount of network throughput both received from and transmitted to clients by each instance in the Neptune DB cluster | Average | MB/sec |
Network Transmit Throughput | The outgoing network traffic on the DB instance, including both customer database traffic and Neptune traffic used for monitoring and replication | Average | MB/sec |
SPARQL Errors | Number of errors in the SPARQL queries | Sum | Count |
SPARQL Requests | The number of requests to the SPARQL engine | Sum | Count |
SPARQL Requests Per Sec | The number of requests to the SPARQL engine per second | Sum | Count/sec |
Status Errors | The number of errors from the status endpoint | Sum | Count |
Status Requests | The number of requests to the status endpoint | Sum | Count |
Http1xx | The number of HTTP 1xx errors for the endpoint per second | Sum | Count/sec |
Http2xx | The number of HTTP 2xx errors for the endpoint per second | Sum | Count/sec |
Http4xx | The number of HTTP 4xx errors for the endpoint per second | Sum | Count/sec |
Http5xx | The number of HTTP 5xx errors for the endpoint per second | Sum | Count/sec |
Gremlin Http1xx | The number of HTTP 1xx errors for the Gremlin endpoint per second | Sum | Count/sec |
Gremlin Http2xx | The number of HTTP 2xx errors for the Gremlin endpoint per second | Sum | Count/sec |
Gremlin Http4xx | The number of HTTP 4xx errors for the Gremlin endpoint per second | Sum | Count/sec |
Gremlin Http5xx | The number of HTTP 5xx errors for the Gremlin endpoint per second | Sum | Count/sec |
Sparql Http1xx | The number of HTTP 1xx errors for the SPARQL endpoint per second | Sum | Count/sec |
Sparql Http2xx | The number of HTTP 2xx errors for the SPARQL endpoint per second | Sum | Count/sec |
Sparql Http4xx | The number of HTTP 4xx errors for the SPARQL endpoint per second | Sum | Count/sec |
Sparql Http5xx | The number of HTTP 5xx errors for the SPARQL endpoint per second | Sum | Count/sec |
Forecast
Estimate future values of the following performance metrics and make informed decisions about adding capacity or scaling your AWS infrastructure.
- CPU Utilization
- Gremlin Errors
- Gremlin Requests
- SPARQL Errors
- SPARQL Requests
Site24x7's Amazon Neptune Instance monitoring tabs
Summary
Gain an overview of different processes occurring within each instance with time series charts that provide event timelines on Gremlin Requests, Gremlin Errors, Network Throughput, SPARQL Errors, and SPARQL Requests.
Configuration Details
The configuration details of an instance are provided under this tab. Here, you'll find the instance state, instance ARN, endpoint URL, engine version, and allocated storage space to name a few.
Events
The events tab contains information on events related to DB instances, DB Security groups, DB snapshots, and DB parameter groups for the past.
Recent Logs
Users can view audit log data of Neptune DB instances that have been published by CloudWatch logs.