CloudWatch custom metrics
Created by Lan Dang on Aug 02, 2016
Confidence Level TBD This article has not been reviewed for accuracy, timeliness, or completeness. Check that this information is valid before acting on it. |
---|
Introduction
When we use Amazon Web Services autoscaling, we need to configure an alarm that is triggered when a certain condition is met. Usually, this involves checking whether a CloudWatch metric falls within or outside a certain range.
Since we want to trigger autoscaling when we have a large number of jobs in the system, Mozart needs to communicate this metric to Amazon, so it can be used in CloudWatch. We can define custom metrics. This is done via https://github.jpl.nasa.gov/hysds-org/hysds/blob/master/scripts/sync_ec2_job_metric.py
The program runs in supervisord on Mozart. This is not enabled by default, because it is customized based on which queues are being monitored. You need to add a new program block for each queue you are monitoring.
This is the templated version kept in GitHub for ARIA Ops:
hysds_cluster_fab/files/supervisord.conf.mozart
Code
|
MONITORED_QUEUE_5 is a template variable defined in hysds_cluster_fab/context.sh
|
Once Fabric pushes the configuration to Mozart, it can be found on Mozart at: /home/ops/mozart/etc/supervisord.conf
|
Related Articles: |
---|
Have Questions? Ask a HySDS Developer: |
Anyone can join our public Slack channel to learn more about HySDS. JPL employees can join #HySDS-Community
|
JPLers can also ask HySDS questions at Stack Overflow Enterprise
|
Page Information: |
---|
Was this page useful? |
Contribution History:
|
Subject Matter Expert: @Gerald Manipon @Hook Hua @Lan Dang |
Find an Error? Is this document outdated or inaccurate? Please contact the assigned Page Maintainer: @Lan Dang |