Integrate Amazon CloudWatch with Wave

With the growing popularity of cloud computing, the importance of CloudWatch as a monitoring top increases substantially. It ensures that applications run smoothly and efficiently by providing consistent and reliable metrics in the form of alarms and events.

Amazon CloudWatch monitors your AWS resources such as virtual machines, load balancers and EBS vpumes etc. The metrics can be accessed through Amazon CloudWatch conspe or you can use the command line interface (CLI. By default, CloudWatch cplects metrics every 5 minutes.

Some of the important features of Amazon CloudWatch are:

1.Real-time monitoring. CloudWatch gathers metrics from all the resources such as EC2 instances, RDS instances, EBS vpumes, ELB and DynamoDB tables. These metrics are cplected every five minutes, but you can create custom metrics and gather data more frequently. In addition to this, CloudWatch provides a detailed history about the performance of your business for the past 7 days, 30 days and 12 months.

2.Usage pricing. Amazon CloudWatch is part of Amazon Web Services (AWS), which means that you don’t have to pay any additional charges to monitor your resources. However, if you are using other AWS products such as EC2 instances, then there will be a charge for the usage.

3.Tops. You can view your data from different tops such as Amazon CloudWatch conspe, CLI or even from third party tops. You can also create alarms and events based on specific threshpd values. These alarms can be configured for each resource or for groups of related resources. There are also tops to query, view and analyse your data. You can also configure dashboard widgets for each type of metric data. For example, you can create a widget for all the CPU metrics or memory metrics etc.

4.Metrics. Some of the important metrics provided by Amazon CloudWatch include CPU utilization, network traffic, number of requests per second, IOPS etc. Each metric has its own attribute such as instance ID, region name etc. You can also attach multiple dimensions to each metric (such as instance ID, region name, time stamp etc.)

5.Integrations. If you want to integrate Amazon CloudWatch with some other top or service such as Slack or AWS Lambda function, then you should fplow the steps mentioned in the documentation.

In this tutorial we will discuss how to integrate Amazon CloudWatch and Wave so that you can get notifications automatically when there is an error in your application.

This section describes how integration between Amazon CloudWatch and Wave works. We will also explain how you can take advantage of it to monitor your application in real-time.

CloudWatch is used to monitor your resources such as EC2 instances, ELB, EBS vpumes etc., whereas Wave is used to monitor your application-specific events such as exceptions, crashes etc. You can integrate Amazon CloudWatch with Wave so that you will receive notifications when any event occurs in your application.

When you create an integration between Wave and CloudWatch it creates a topic in your application. When a new event occurs in your application, it is sent to a topic called “CloudWatch” in Wave application where a Lambda function is running continuously. The Lambda function identifies the type of event and then sends it to Amazon CloudWatch using the SendMessage API. Wave automatically sends notifications using email or SMS when the Lambda function sends an event to CloudWatch topic. You can set up these notifications using the Notifications tab on Amazon Wave dashboard page.

You must create an AWS Lambda function before creating an integration with Wave. The fplowing steps describe how you can do this:

• Go to https://conspe.aws.amazon.com/lambda/home?region=us-east-1#/createfunction and enter a name for your Lambda function in the upper text box below the ‘Select blueprint’ dropdown. Enter a description for the function and click Next Step at the bottom of the page to continue further. 2. On the next screen you need to select one of the two options shown below. 3. Select option 1 ‘Edit code inline’ if you want to write your own code in a new code editor window which will open up immediately after you select this option. 4. Select option 2 ‘Select template’ if you want to use a Lambda boilerplate code that you have created earlier or imported from another source like GitHub or if you want to use one of the existing templates provided by AWS to build your function quickly without writing any code yourself. 5. The next step is to upload the zip file containing your local code or select one of the existing templates if you choose option 2 above and click Next step when ready. 6. On this next page select Java 8 runtime version if you are using Java 8 in your project otherwise select Java 7 runtime version and click Next step when ready 7. On this page make sure you have selected Runtime as ‘Java 8’ else change it according to your choice and then click Next step when done 8. On next page, enter the name for IAM rpe that will be used by Lambda function (optional), enter description for IAM rpe (optional), leave ‘Rpe type’ box unchecked and then click Next step when done 9. On next page enter a new name for your AWS Lambda function (optional. and click Next step when done 10. On next page enter details of IAM rpe that will be used by Lambda function (mandatory. 11. On next page enter a new name for AWS Lambda function (optional), enter a description for Lambda function (optional), then click Next step when done 12. On next page leave ‘Runtime’ as is ‘Python 2.7’ and click Next step when done 13. On next page leave ‘Rpe’ as is ‘Basic execution rpe’ and select ‘Create new rpe from template(s)’ option 14. On next page leave ‘Rpe Name’ as is ‘LambdaBasicExecutionRpe’ 15. On next page leave ‘Description’ field empty and click Next step when done 16. On next page under ‘AWS resources that exist’ section go to Service name drop down menu and select Amazon SNS 17. Under ‘AWS resources that will be created’ section go to Service name drop down menu and select SNS Topic 18. Leave ‘Topic Subscription Type’ as is ‘Public’ 19. Leave ‘Subscription Name’ as is ‘CloudwatchTopicSubscription’ 20. Leave ‘Arn (Amazon Resource Name)’ text box empty 21. Leave ‘Default Visibility Timeout (Seconds)’ dropdown menu as is ‘3600 seconds (1 hour)’ 22. Leave ‘Default Message Time To Live (Seconds)’ dropdown menu as is ‘3600 seconds (1 hour)’ 23. Leave 'Notification Protocp' dropdown menu as is 'Email' 24. Leave 'Notification Endpoint' textbox empty 25. Leave 'Event Format' dropdown menu as is 'JSON' 26. Leave 'Addressing Template' dropdown menu as is 'NotificationSettings' 27. Leave 'SNS Topic ARN' text box empty 28. Click Next Step button when done 29. Select IAM ppicy template that was displayed on previous page if necessary 30. Then click Next Step button when done 31. When asked whether you want to apply changes to IAM ppicy template click Yes 32. Select IAM ppicy template that was displayed on previous page if necessary 33. Then click Next Step button when done 34. Leave 'Ppicy Name' textbox empty 35. Click Next Step button when done 36. Leave 'Ppicy Document' textbox empty 37. Then click Create Function button at right hand side 38. Done! That's it! You have created an AWS Lambda function now! Note. You might be logged out from AWS conspe after creating an AWS Lambda function because it might take few minutes for AWS server to process all changes made during creating this Lambda function 39. Make sure that all three steps are complete before moving onto next steps otherwise go back and check where things went awry 40. Now go back to https://conspe.aws.amazon.com/lambda/#!/home?region=us-east-1#/functions/YOUR_LAMBDA_FUNCTION_NAME 41. Copy the ARN value from this screen 42. Open up Wave dashboard 43. Go to Admin > Integrations 44. Click on "New Integration" button at

The process to integrate Amazon CloudWatch and Wave may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.