Skip to content

Fix Bot Insights ai_category transform output#184

Open
tom-howe-hdx wants to merge 2 commits into
mainfrom
fix-bot-insights-ai-category
Open

Fix Bot Insights ai_category transform output#184
tom-howe-hdx wants to merge 2 commits into
mainfrom
fix-bot-insights-ai-category

Conversation

@tom-howe-hdx

Copy link
Copy Markdown
Collaborator

Summary

  • add ai_category output columns to manifest-listed Bot Insights transforms that feed the shared logs table
  • populate ai_category from commons_ua_cat_dict for Akamai DS2, CloudFront Firehose, and Fastly
  • emit NONE for Cloudflare to match its existing placeholder bot classification path

Why

The Bot Insights summary tables and dashboard query ai_category, but several transforms did not materialize that column. Deploy-time summary creation can fail with Missing columns: ai_category when the parent table schema is built from those transforms.

Validation

  • jq empty on the changed transform JSON files
  • verified every transform listed in aws/bot-insights/bundle.json now exposes ai_category
  • cargo run -- bot_insights

Not Run

  • cluster-backed deploy validation; local BUNDLE_TESTING_CLUSTER, BUNDLE_TESTING_USERNAME, and BUNDLE_TESTING_PASSWORD are unset

@tom-howe-hdx tom-howe-hdx temporarily deployed to bundle-validator-env April 22, 2026 20:42 — with GitHub Actions Inactive
Normalize settings.sample_data from array to single dict across all six
transforms so the deploy path's sample extractor actually ingests rows
(previously only tencent's dict form passed through; the five array-typed
transforms silently skipped both insert and verification). Also promote
default's rich 23-field external sample_data.json content into the
embedded transform copy so test ingests land a realistic row rather than
just a {timestamp} stub. Fix a Go-layout typo in tencent's primary format
(15:05:05Z -> 15:04:05Z).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants