Visualization of RDS metrics using AWS CLI and JQuery at AWS Usergroup Leipzig
0 likes180 views
Andreas Ulm (root360 GmbH) at AWS Usergroup Leipzig about visualization of RDS metrics using AWS CLI and JQuery
![Enhanced Monitoring Logs
• every collected metric data is in Cloudwatch Logs
• log group name: RDSOSMetrics
• log stream name: <DbiResourceId>
• get by running: “aws rds describe-db-instances --query 'DBInstances[].
[DBInstanceIdentifier,DbiResourceId]'
• json format
• retrieved using “aws logs get-log-events --log-group-name
RDSOSMetrics --log-stream-name <DbiResourceId>”
6](https://image.slidesharecdn.com/visualizerdsmetricsusingawscliandjquery-reallifeexample-awsug04-02-2016-160209083928/85/Visualization-of-RDS-metrics-using-AWS-CLI-and-JQuery-at-AWS-Usergroup-Leipzig-6-320.jpg)
![[AWSKRUG&JAWS-UG Meetup #1] 70% Cost Reduction with On-demand resizing](https://cdn.slidesharecdn.com/ss_thumbnails/awsjawsondemandresizing-160526114219-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
What's hot (16)
Viewers also liked (9)
Ad
Similar to Visualization of RDS metrics using AWS CLI and JQuery at AWS Usergroup Leipzig (18)
Ad
Recently uploaded (20)
Visualization of RDS metrics using AWS CLI and JQuery at AWS Usergroup Leipzig
- 1. Visualize RDS metrics using AWS CLI and JQuery 1 Andreas Ulm <[email protected]> Senior Cloud Architect root360 GmbH AWS Certified Solutions Architect - Associate Level AWS user group Leipzig – 4.2.2016
- 2. System • Shopware • webserver in ASG • RDS (master-slave replication) • no read-replica 2
- 3. Issue • high request rate on webserver • Shopware slows down • 503 HTTP errors due to timeout of PHP 3
- 4. Cloudwatch Graphs • no peak or plateau visible • no AWS limit seems to be reached 4
- 5. Enhanced Monitoring Graphs • “there is something fishy” • “I need a bigger timeframe” 5
- 6. Enhanced Monitoring Logs • every collected metric data is in Cloudwatch Logs • log group name: RDSOSMetrics • log stream name: <DbiResourceId> • get by running: “aws rds describe-db-instances --query 'DBInstances[]. [DBInstanceIdentifier,DbiResourceId]' • json format • retrieved using “aws logs get-log-events --log-group-name RDSOSMetrics --log-stream-name <DbiResourceId>” 6
- 7. Who can see the issue? 7
- 8. Self-made Plotting • run bash script • retrieve data • convert data to valid json • prepare data for plotting • open index.html in browser • load prepared json data • plot data using flot library 8
- 9. Our Graphs • there is a plateau !! • AWS limit is reached in disk IO 9
- 10. RDS Disk IO • specified in AWS documentation • RDS • EBS • used IOPS < base IOPS => credits increase • used IOPS > base IOPS => credits reduced per second • burst up to 3000 IOPS • credits = 0 => usable IOPS reduced & limited 10
- 11. Solution • limit active => system very slow • system need more base IOPS • either, increase volume size • 3 IOPS per GB volume size • max. 3,000 IOPS using volume size >= 1 TB • or, use provisioned IOPS • MySQL: 1,000 - 30,000 IOPS • SQL Server Express: 1,000 - 20,000 IOPS • we use provisioned IOPS 11
- 12. Demo 12
- 13. Code • available on Github: https://github.com/root360/AWS-RDS- enhanced_monitoring • license: Unlicense http://unlicense.org/ • use it • change it • publish/distribute it • or don’t ;-) • feedback: [email protected] 13
- 14. Open Topic e.g.: • Questions • multi account strategies • RDS vs Aurora (tests, best practice, migration, compatibility) • SES Limitations • Server-Monitoring (RAM, CPU, SSD) • YOUR TOPIC 14