Appendix F: Collection of Operational Metrics - Operations Conductor

Appendix F: Collection of Operational Metrics

This solution includes an option to send anonymous operational metrics to AWS. We use this data to better understand how customers use this solution and related services and products. When enabled, the following information is collected and sent to AWS:

  • Solution ID: The AWS solution identifier

  • Version: The solution version

  • Unique ID (UUID): Randomly generated, unique identifier for each solution deployment

  • Timestamp: Data-collection timestamp

  • Event Type: An identifier for what event occured

  • Event Data: Details about the event

The table below shows the events that will result in the collection of operational metrics.

Event Type Evevnt Data
Scheduled Task Created
  • Task Name

  • Automation Document Name

  • Region Count (the number of regions the task will be executed in)

  • Account Count (the number of accounts the task will be executed in)

  • Schedule Type (Fixed Rate or Cron)

  • Schedule Details (Rate Type and Interval or Cron expression)

Event Task Created
  • Task Name

  • Automation Document Name

  • Region Count (the number of regions the task will be executed in)

  • Account Count (the number of accounts the task will be executed in)

  • Event Service Name (the AWS service that triggers the event)

  • Event States (the resource state changes events that trigger the event)

Task Deleted
  • Task Name

Task Executed Manually
  • Task Name

  • Automation Document Name

  • Region Count (the number of regions the task will be executed in)

Task Executed by Event
  • Task Name

  • Automation Document Name

  • Region Count (the number of regions the task will be executed in)

Task Executed by Schedule
  • Task Name

  • Automation Document Name

  • Region Count (the number of regions the task will be executed in)

Failed Task Executions
  • Task Name

  • Automation Document Name

Note that AWS will own the data gathered via this survey. Data collection will be subject to the AWS Privacy Policy. To opt out of this feature, complete one of the following tasks: a) Modify the AWS CloudFormation template mapping section as follows:

Send: AnonymousUsage: Data: "Yes"

to

Send: AnonymousUsage: Data: "No"

b) After the solution has been launched, find the User Service, Task Service, and Resource Selector functions in the Lambda console, and set the SendAnonymousUsageData environment variable to No.