Skip to content

feat(server-ai): stamp modelKey and modelVersion on AI usage events (…#308

Draft
atornsii wants to merge 1 commit into
mainfrom
atornsii/AIC-2856/net-add-model-key-version
Draft

feat(server-ai): stamp modelKey and modelVersion on AI usage events (…#308
atornsii wants to merge 1 commit into
mainfrom
atornsii/AIC-2856/net-add-model-key-version

Conversation

@atornsii

@atornsii atornsii commented Jul 8, 2026

Copy link
Copy Markdown

…AIC-2856)

Read modelKey and modelVersion from the AI Config variation payload and stamp them on all LdAiConfigTracker metric event payloads alongside existing modelName/providerName fields.

  • Add ModelKey/ModelVersion to ModelConfig
  • Parse new fields from variation payload in ConfigFactory
  • Include modelVersion unconditionally (default 1) and modelKey when non-empty in track data; exclude both from resumption token
  • Additive/backward compatible — older payloads without the new fields continue to work

Part of AIC-2849. Depends on AIC-2876 (backend payload).

Requirements

  • I have added test coverage for new or changed functionality
  • I have followed the repository's pull request submission guidelines
  • I have validated my changes against all supported platform versions

Related issues

Provide links to any issues in this repository or elsewhere relating to this pull request.

Describe the solution you've provided

Provide a clear and concise description of what you expect to happen.

Describe alternatives you've considered

Provide a clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context about the pull request here.

…AIC-2856)

Read modelKey and modelVersion from the AI Config variation payload and stamp
them on all LdAiConfigTracker metric event payloads alongside existing
modelName/providerName fields.

- Add ModelKey/ModelVersion to ModelConfig
- Parse new fields from variation payload in ConfigFactory
- Include modelVersion unconditionally (default 1) and modelKey when non-empty
  in track data; exclude both from resumption token
- Additive/backward compatible — older payloads without the new fields continue
  to work

Part of AIC-2849. Depends on AIC-2876 (backend payload).

Co-authored-by: Anthony Torns II <atornsii@users.noreply.github.com>
@jsonbailey

Copy link
Copy Markdown
Contributor

Holding based on our conversation today and we will follow up on slack before reviewing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants