Slide 18
Slide 18 text
© Hitachi, Ltd. 2024. All rights reserved.
Information that can be obtained
✓ Start and end timings of events (failures or load spikes)
✓ Error rate, latency, resource consumption before, during, and after the event
✓ Changes in Java connection count, Java thread count, and other metrics
Use case examples
1. Failure testing:
Investigate how the duration of frontend errors changes during DB failover when
RDS Proxy is introduced.
2. Performance testing:
Test if resource consumption under load remains below the specified limits and
investigate the components causing bottlenecks for potential improvements.
3. Proof of Concept:
Investigate how the response time for database access changes when a cache
server is introduced.
Concept of analysis with OTel
17
[{
"name": "my_aurora_db",
"start_time": "2024-06-19T12:00:00Z",
"end_time": "2024-06-19T12:01:00Z",
"abnormal_time_seconds": 60,
"metrics": {
"before_abnormal": {
"average_latency_ms": 50,
"total_errors": 0,
"error_percentage": 0.0,
"requests_per_second": 200,
"cpu_usage_percentage": 30.0,
"memory_usage_mb": 2048,
"read_iops": 600,
"write_iops": 400,
"retry_attempts": 0,
"cache_hit_ratio": 95.0,
"connection_errors": 0,
"transaction_rollbacks": 0
},
"under_abnormal": {
"average_latency_ms": 250,
"total_errors": 150,
"error_percentage": 5.0,
"requests_per_second": 80,
"cpu_usage_percentage": 75.0,
"memory_usage_mb": 4096,
"read_iops": 1200,
"write_iops": 800,
"retry_attempts": 20,
"cache_hit_ratio": 85.0,
"connection_errors": 30,
"transaction_rollbacks": 10
},
"after_abnormal": { ... }
}
},
{
"name": "backend_app",
...
}]
Example analysis output
behavior
before
a failure
behavior
during
the failure
anomaly
time
Target component
behavior
after
the failure