Monitoring and Usage Tracking in AWS Deep Learning Containers
Your AWS Deep Learning Containers do not come with monitoring utilities. For information on monitoring, see GPU Monitoring and Optimization, Monitoring Amazon EC2, Monitoring Amazon ECS, Monitoring Amazon EKS, and Monitoring Amazon SageMaker Studio.
Usage Tracking
AWS uses customer feedback and usage information to improve the quality of the services and software we offer to customers. We have added usage data collection to the supported AWS Deep Learning Containers in order to better understand customer usage and guide future improvements. Usage tracking for Deep Learning Containers is activated by default. Customers can change their settings at any point of time to activate or deactivate usage tracking.
Usage tracking for AWS Deep Learning Containers collects the instance ID, frameworks, framework versions, container types, and Python versions used for the containers. AWS also logs the event time in which it receives this metadata.
No information on the commands used within the containers is collected or retained. No other information about the containers is collected or retained.
To opt out of usage tracking, set the OPT_OUT_TRACKING
environment
variable to true.
OPT_OUT_TRACKING=true
Failure Rate Tracking
When using a first-party Amazon SageMaker AWS Deep Learning Containers
container
Failure rate tracking for AWS Deep Learning Containers collects the Instance ID, ModelServer name, ModelServer version, ErrorType, and ErrorCode. AWS also logs the event time in which it receives this metadata.
No information on the commands used within the containers is collected or retained. No other information about the containers is collected or retained.
To opt out of failure rate tracking, set the OPT_OUT_TRACKING
environment variable to true
.
OPT_OUT_TRACKING=true
Usage Tracking in the following Framework Versions
While we recommend updating to supported Deep Learning Containers,
to opt-out of usage tracking for Deep Learning Containers that use these frameworks,
set the OPT_OUT_TRACKING
environment variable to true and
use a custom entry point to disable the call for the following services: