Important: Application Monitoring solution has been retired. We encourage customers to explore using Amazon CloudWatch to set up observability for Apache, NGINX and PUMA workloads running on Amazon Elastic Cloud Compute (Amazon EC2). You can also find other solutions in the AWS Solutions Library.
🚀Solution Landing Page | 🚧Feature request | 🐛Bug Report | 📜Documentation Improvement
Note: For any relevant information outside the scope of this readme, please refer to the solution landing page and implementation guide.
- Solution Overview
- Architecture
- Customization
- Supported CloudWatch Widgets
- Configuring Instances
- Adding Workloads
- File Structure
- License
- Operational Metrics
Application Monitoring with Amazon CloudWatch is intended for customers looking to easily gain actionable insight into their EC2 workloads. The process to configure cloudwatch agent, identify the right metrics, logs and create dashboard to seeg workload performance can be tedious and time-consuming.
The solution automates the process of dashboard setup and provides reference config files for some of the most common workloads. Using a tagging mechanism you can identify the instances you want to be monitored on the dashboard. The solution makes it easy for the customers to focus on workload KPIs rather than spending time on setting up the needed dashboards.
The solution follows nested stack approach for deployment of workload stacks. The workload stacks can be deployed individually as well.
The architecture can be broken into two components. User Interaction and Dashboard Management. The workflow is as follows:
- User puts tag on the EC2 instance
- tagHandler lambda function fetches instances with the tag and updates SSM Parameter Store
- CloudWatch Events rule gets triggered when SSM parameter is updated, and invokes dashboardHandler lambda function
- dashboardHandler lambda function reads the SSM parameter and updates the CloudWatch dashboard widgets
- Prerequisite: Node.js>=14 | npm >= 7
Clone the repository and run the following commands to install dependencies, format and lint as per the project standards
npm ci
npm run prettier-format
npm run lint
You may make any needed change as per your requirement. If you want to change the workload dashboard configurations, modify the relevant manifest file. For eg. for Apache you would change apache exports. Also see Example Scenario: Custom Metrics.
Additionally, you can customize the code and add any extensibility to the solution. Please review our feature request guidelines, if you want to submit a PR.
You can run unit tests with the following command from the root of the project
npm run test
You can build lambda binaries with the following command from the root of the project
npm run build
The solution has following CDK Stacks
- Framework Stack: this stack controls provisioning of individual workload related resources
- Workload Stack: this stack deploys resources to monitor the workload and put logs & metrics on the dashboard
- Demo Stack: this stack creates a single instance to showcase solution capabilities in monitoring the workload
Run the following command from the root of the project
cd source/resources
npm ci
npm run cdk-bootstrap -- --profile <PROFILE_NAME>
npm run cdk-synth
npm run cdk-deploy -- CW-Monitoring-Framework-Stack --parameters ApacheDemoInstance=No --parameters NginxDemoInstance=No --parameters PumaDemoInstance=No --profile <PROFILE_NAME>
To destroy deployed stack
npm run cdk-destroy CW-Monitoring-Framework-Stack --profile <PROFILE_NAME>
Please follow this section to customize default set of metrics monitored by the solution for the workload. Let's say we want to add cpu_usage details for amazon-cloudwatch-agent on the apache dashboard. (We assume that CloudWatch agent on your EC2 instance is sending these metrics to CloudWatch.) In this case you would need to update the apache_exports.ts.
Since this would be a multi-dimensional metric, we need to update the metricWidget in apache_exports.ts as follows:
[
[
"CWAgent",
"procstat_cpu_usage",
"exe",
"httpd",
"InstanceId",
"%%instance%%",
"process_name",
"httpd",
],
[
"CWAgent",
"procstat_cpu_usage",
"exe",
"amazon-cloudwatch-agent",
"InstanceId",
"%%instance%%",
"process_name",
"amazon-cloudwatch-agent",
]
]
To read more about supported widgets and metrics types, refer to Supported CloudWatch Widgets
Now, we need to rebuild the microservice dashboardHandler:
cd source/services/dashboardHandler
npm run build:all
Follow the steps from Build and Deploy to deploy the updated apache dashboard.
The framework currently supports following widget types
- Log widgets: to capture cloudwatch log insights queries
- Metric explorer widget: to capture metrics with single dimension
- Metric widget: to capture metrics with more than one dimension
reference: generics.ts
The solution does not configure your EC2 instances. You need to ensure that your instances our configured correctly and sending CloudWatch metrics and logs in the needed format. For eg. if you have apache workload instances, you should refer to following cloudwatch agent configuration files, the same files are used to bootstrap our demo instance.
- base configuration file - base infrastructure cloudwatch agent configuration
- apache configuration file - apache related cloudwatch agent configuration
- httpd.conf - apache web server config for error and access log format
Note: If the instances do not send needed metrics and logs to CloudWatch in needed format, the dashboard will not show data points from those instances.
Currently, the framework supports apache, nginx and ruby/puma workload. We will continue to add more workloads. Each workload deploys as a nested stack on the framework and has its own infrastructure resources. This removes any infrastructure dependency between workloads, and also allows to easily turn on/off individual workloads.
To extend the framework follow given steps:
Add infrastructure resources to support the workload.
- exports.ts Extend Workload export for the new workload.
- framework.infra.ts Update the framework stack, parameters conditions and resources sections to deploy nested stack for the new workload and the demo instance
- /source/resources/lib/workload: Create the folder for the new workload
- workload.config: Add reference configuration files for the cloudwatch agent and workload instance. The configuration files will determine the metrics and logs being pushed to Amazon CloudWatch. reference: apache.config The metrics, log and log format identified in the config files must be consistent with dashboard widget manifest file reference: apache_exports.ts.
- workload.demo.ts: Add demo instance to create sample web server, bootstrapped with reference configurations files. reference: apache.demo.ts
We need to extend dashboardHandler lambda function for new workloads
- /source/services/dashboardHandler/lib/widgets/workload_exports.ts: Create the manifest file for Log Widget, Metric Explorer Widget and Metric Widget configuration. You can specify the metrics, logs and widgets that you would like to show up on the dashboard for the workload. Please also see Supported CloudWatch Widgets section. reference: apache_exports.ts
- widget_exports.ts - Extend the WorkloadWidgets export for the new workload
Note: Workload name in resource export file and widget export file must be consistent (case-sensitive) with each other
Application Monitoring with Amazon CloudWatch solution consists of:
- cdk constructs to generate needed infrastructure resources
- tagHandler to validate tag, identify EC2 resources with the tag and update SSM parameter with instance-ids
- dashboardHandler to update dashboard for the workload with metrics and logs
- helper functions for solution purposes
- utils library for generic utility functions like logging and metrics
|-deployment/
|build-scripts/ [ build scripts ]
|-source/
|-resources
|-bin/
|-cw-monitoring-framework.ts [ entry point for CDK app ]
|-__tests__/ [ unit tests for CDK constructs ]
|-lib/
|-workload [ workload artifacts ]
|-workload.config/ [ workload configs ]
|-workload.demo.ts [ workload demo EC2 instance CDK construct ]
|-demo.infra.ts [ CDK construct for generic demo resources ]
|-framework.infra.ts [ CDK stack framework resources ]
|-workload.infra.ts [ generic CDK stack for workload resources ]
|-exports [ manifest file for framework and workload stacks ]
|-app-registry [CDK constructs for creating app registry resources]
|-config_files [ tsconfig, jest.config.js, package.json etc. ]
|-services/
|-helper/ [ lambda helper custom resource to help with solution launch/update/delete ]
|-utils/ [ library with generic utility functions ]
|-dashboardHandler/ [ microservice to handle dashboard update ]
|-__tests/ [ unit tests for dashboard handler ]
|-lib/
|-widgets [ CloudWatch dashboard widget configuration files for workloads ]
|-CWHelperAbstract.ts [ abstract class for workloads ]
|-CWWidgetFactory.ts [ generic class to generate widgets using widget-configuration file ]
|-SSMHelper.ts [ class for SSM parameter store operations ]
|-generics.ts [ generic interfaces for the application ]
|-index.ts [ entry point for lambda function]
|-config_files [ tsconfig, jest.config.js, package.json etc. ]
|-tagHandler
|-__tests/ [ unit tests for tag handler ]
|-lib/
|-EC2Helper.ts [ class for EC2 tag operations ]
|-TagHandlerSSMHelper.ts [ class for SSM parameter store operations ]
|-index.ts [ entry point for lambda function]
|-config_files [ tsconfig, jest.config.js, package.json etc. ]
|-config_files [ eslint, prettier, tsconfig, jest.config.js, package.json etc. ]
See license here
This solution collects anonymized operational metrics to help AWS improve the quality and features of the solution. For more information, including how to disable this capability, please see the implementation guide.
Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
Licensed under the Apache License Version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at
http://www.apache.org/licenses/LICENSE-2.0
or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied. See the License for the specific language governing permissions and limitations under the License.