CloudWatch Integration

Cloud Watch can be used for monitoring BI Events and Internal Redis Queues.
BI Events are events or metrics that are collected whenever an user perform some action during Comet application usage.
Internal Redis queues monitoring is useful for investigating technical issues with the application

Cloud Watch BI Events/Metrics¶

In order to enable it, you may want to set the following environment variables. If its a Linux deployment, you can add them in your /etc/default/comet-ml file.

BI_ENABLED="True"
AWS_CLOUD_WATCH_KEY=""
AWS_CLOUD_WATCH_SECRET=""
AWS_CLOUD_WATCH_SOURCE="comet_onprem"
AWS_CLOUD_WATCH_BI_ENABLED="True"
AWS_CLOUD_WATCH_REGION="us-east-1"

When is a kubernetes deployment, add can append those variables in your backend.additionalConfigurations section in your values.yaml like:

backend:
  additionalConfigurations:
    BI_ENABLED: "true"
    AWS_CLOUD_WATCH_KEY: ""
    AWS_CLOUD_WATCH_SECRET: ""
    AWS_CLOUD_WATCH_SOURCE: "comet_onprem"
    AWS_CLOUD_WATCH_BI_ENABLED: "True"
    AWS_CLOUD_WATCH_REGION: "us-east-1"

Cloud Watch Redis Queue monitoring¶

To enable internal monitoring application Redis queues, the following variables are relevant

AWS_CLOUD_WATCH_MONITORING_ENABLED="True"
AWS_CLOUD_WATCH_KEY=""
AWS_CLOUD_WATCH_SECRET=""
AWS_CLOUD_WATCH_SOURCE="comet_onprem"

or

backend:
  additionalConfigurations:
    AWS_CLOUD_WATCH_MONITORING_ENABLED: "True"
    AWS_CLOUD_WATCH_KEY: ""
    AWS_CLOUD_WATCH_SECRET: ""
    AWS_CLOUD_WATCH_SOURCE: "comet_onprem"

Here's a JSON example to import in your CloudWatch dashboard [---[% import 'cloudwatch-redis-q-em.json' as cloudwatch_redis_q %]---]

[---[ cloudwatch_redis_q ]---]