Viewing per-user activity

You can export daily per-user activity telemetry for the Kiro subscribers in your organization. Use these exports to audit usage, optimize license allocation, track credit and overage consumption, and understand how individual users interact with Kiro across clients.

Kiro offers two independent export formats. You can enable either format or both:

Both formats contain the same daily aggregate usage metrics. The OpenTelemetry export transforms those metrics to OTLP.

Each day at 02:00 UTC, Kiro generates a CSV report per Kiro client type (IDE, CLI, and Plugin) and writes it to your S3 bucket.

s3://bucketName/prefix/AWSLogs/accountId/KiroLogs/user_report/region/year/month/day/00/clientType_accountId_user_report_timestamp.csv

Create an Amazon S3 bucket to hold the user activity report CSV file. The bucket must:

• Be in the AWS Region where the Kiro profile was installed. This profile was installed when you subscribed IAM Identity Center workforce users to Kiro Pro for the first time. For more information about this profile and the Regions where it's supported, see Kiro profile and Supported Regions.

• Be in the AWS account where users are subscribed. If users are subscribed in multiple AWS accounts, then you must create buckets in each of those accounts. Cross-account buckets are not supported.

• (Optional but recommended) Be different from the bucket you might be using for logging users' prompts.

• Include a prefix, also known as a subfolder, where Kiro will save the CSV file. The CSV file cannot be saved in the root of the bucket.

• Have a bucket policy like the one that follows. Replace bucketName, prefix, region, and accountId with your own information. The region and accountId in the policy's Condition block must match the Region where your Kiro profile was installed and the AWS account where users are subscribed.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "KiroLogsWrite",
      "Effect": "Allow",
      "Principal": {
        "Service": "q.amazonaws.com"
      },
      "Action": [
        "s3:PutObject"
      ],
      "Resource": [
        "arn:aws:s3:::bucketName/prefix/*"
      ],
      "Condition": {
        "StringEquals": {
          "aws:SourceAccount": "accountId"
        },
        "ArnLike": {
          "aws:SourceArn": "arn:aws:codewhisperer:region:accountId:*"
        }
      }
    }
  ]
}

To learn about protecting the data in your Amazon S3 bucket, see Protecting data with encryption in the Amazon Simple Storage Service User Guide.

1. Sign in to the AWS console.

2. Switch to the Kiro console. To use the Kiro console, you must have the permissions defined in Policy: Allow administrators to configure Kiro and subscribe users.

3. Choose Settings.

4. Under Kiro user activity reports, choose Edit.

5. Toggle Collect granular metrics per user.

6. Under S3 location, enter the Amazon S3 URI that you will use to hold the CSV reports. Example: s3://amzn-s3-demo-bucket/user-activity-reports/

The first CSV report is generated at the next 02:00 UTC cycle after you enable reporting, and new files are written every day afterward. Once reports are in your bucket you can query them with Amazon Athena, visualize trends in Amazon QuickSight, or pull them into your existing analytics pipeline.

For a higher-level view of Kiro usage without per-user detail, see Viewing Kiro usage on the dashboard. To also capture the content of user prompts, see Prompt logging.

Each CSV contains static columns and dynamic per-model message columns.

The number of *model_name*_messages columns depends on the models used on the report date. These columns use lowercase model names in alphabetical order, starting with Auto. A column contains 0 when a user didn't use that model during the report day.

The legacy user activity report continues to run alongside the per-client report and contains CLI and plugin usage. Its daily CSV files are published to the same S3 bucket at this path:

s3://bucketName/prefix/AWSLogs/accountId/KiroLogs/by_user_analytic/Region/year/month/day/00/accountId_by_user_analytic_timestamp.csv

The 00 segment is a fixed hour partition for the 02:00 UTC write cycle. In each file:

• Each row represents a user who interacted with Kiro that day.
• Each column contains one of the legacy metrics listed below, calculated from the user telemetry collected during the day.
• If more than 1,000 users interact with Kiro during the day, Kiro splits the data into files containing 1,000 users each. Files are suffixed with part_1, part_2, and so on.

The following table describes the legacy metrics that are included in the user activity reports generated by Kiro.