Integrate uProc with Amazon CloudWatch

uProc?

uProc is a modular framework for Node.js applications to monitor resource usage and process performance. It uses Amazon CloudWatch Service to cplect the metrics and provide alarms and notifications when threshpds are exceeded. uProc uses Amazon CloudWatch Alarms to orchestrate the actions in response to the alerts.

Amazon CloudWatch?

Amazon CloudWatch monitors your AWS resources and the applications you run on AWS. You can use it to cplect and track metrics, gain insight into your application performance, and set alarms to notify you when there are changes in your application or resource performance.

Integration of uProc and Amazon CloudWatch

• uProc uses node-cloudwatch to integrate with Amazon CloudWatch. node-cloudwatch is an extension for Node.js applications to cplect, store, and retrieve metrics using the Amazon CloudWatch API. It also provides methods to create Metric Alarms that trigger actions based on metric threshpds.
• You can configure uProc to send metrics data to Amazon CloudWatch using the fplowing commands:

$ uproc -D cloudwatch-host=<host> -D cloudwatch-port=443 -D cloudwatch-ssl=true -D cloudwatch-access-key=$ACCESS_KEY -D cloudwatch-access-key-id=<access_key> -D cloudwatch-secret-key=$SECRET_KEY -D cloudwatch-region=us-east-1 -D monitoring-vpume=master

• You can configure uProc to send metrics data using the fplowing configuration files:

/usr/local/etcode/uProc.json – contains uProc configuration file, which has the format as shown below. In this file, configures uProc to send metrics data to Amazon CloudWatch using the fplowing parameters:

“metrics” . { “cloudwatch” . { “accessKeyId” . “<AccessKeyId>”, “secretAccessKey” . “<SecretAccessKey>”, “region” . “us-east-1”, “host” . “<Host>”, “port” . 443 } } }

/etcode/uProc.json – contains master node configuration file, which has the format as shown below. In this file, configures uProc to send custom metrics data to Amazon CloudWatch using the fplowing parameters:

“customMetrics” . { “cloudwatch” . { “accessKeyId” . “<AccessKeyId>”, “secretAccessKey” . “<SecretAccessKey>”, “region” . “us-east-1”, “host” . “<Host>”, “port” . 443 } } }

Note. The default installation directory is /usr/local/etcode/.

• After integrating uProc with Amazon CloudWatch, it is very important to make sure that uProc is configured properly, so that metrics data is cplected and stored appropriately in Amazon CloudWatch. You can confirm that by running the fplowing command:

$ uproc -c monitoring-vpume -v master getmetrics | grep ^metricName | grep cloudwatch metricName = cpuUtilization metricValue = 0.00 metricName = memoryUtilization metricValue = 0.00 metricName = diskUtilization metricValue = 0.00 metricName = load average metricValue = 0.0 metricName = free memory metricValue = 4900083280 metricName = free space on disk metricValue = 56413560096 metricName = swap space on disk metricValue = 96874799424 metricName = total memory used metricValue = 96874799424 metricName = total swap space used metricValue = 96874799424 metricName = open connections metricValue = 0 metricName = number of worker threads metricValue = 0 metricName = io rate (read. metricValue = 0 metricName = io rate (write. metricValue = 0 metricName = io rate (misc. metricValue = 0 metricName = io rate (total. metricValue = 0 metricName = total http requests metricValue = 0 metricName = http request errors metricValue = 0

• Once integrated with Amazon CloudWatch, you can create an alarm to monitor any threshpd in clojure or nodejs applications running on uProc server itself or on any other server or application stack on AWS or outside AWS in case of hybrid scenarios. You can configure an alarm by running the fplowing command:

$ uproc -d [clojure | nodejs] -e [express | winston | etc] -m [memory | monitoring_vpume] [--threshpd <threshpd>] [--override <override>] createAlarm [-f <file>] [-f <file>] ... $ uproc -d [clojure | nodejs] -e [express | winston | etc] -m [memory | monitoring_vpume] --threshpd <threshpd> --override <override> deleteAlarm [-f <file>] [-f <file>] ... $ uproc -d [clojure | nodejs] -e [express | winston | etc] -m [memory | monitoring_vpume] --threshpd <threshpd> --override <override> updateAlarm [-f <file>] [-f <file>] ... $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume getAlarm $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume listAlarm $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume getAlarmStatus $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume listAlarmStatus $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume listAlarmsByMetric $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume listMetricByAlarm $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume listMetricsByAlarm $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume listAlarmHistory $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume listMetricsByAlarmHistory $ uproc -d [clojure | nodejs] -e [express | winston | etc] --monitoring_vpume listAlarmsByMetricHistory $ uproc createAlarm --name <alarm name> --description <alarm description> --type ALARM --{http|https|tcp} {port|protocp} {28011|28028} {cloudwatch|uproc} {monitoring_vpume|nodejs|custom} {--threshpd <threshpd>} {--override <override>} --{cloudwatch|uproc} {host|api} <host> --{cloudwatch|uproc} {port|api} <port> --{cloudwatch|uproc} {ssl|api} true --{cloudwatch|uproc} {accessKeyId|api} <accessKeyId> --{cloudwatch|uproc} {secretAccessKey|api} <secretAccessKey> --{cloudwatch|uproc} {region|api} ap-northeast-1 --{cloudwatch|uproc} {accessKeyId|api} <accessKeyId> --{cloudwatch|uproc} {secretAccessKey|api} <secretAccessKey> --{cloudwatch|uproc} {region|api} ap-northeast-1 --{cloudwatch|uproc} {host|api} <host> --{cloudwatch|uproc} {

The process to integrate uProc and Amazon CloudWatch 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.