Skip to content

Usage events send event_key for deduping event emission retries for the same event - #69610

Open
charlestp wants to merge 1 commit into
charles/client-kind-user-agentfrom
charles/prehog-event-key
Open

Usage events send event_key for deduping event emission retries for the same event#69610
charlestp wants to merge 1 commit into
charles/client-kind-user-agentfrom
charles/prehog-event-key

Conversation

@charlestp

Copy link
Copy Markdown
Contributor

Another fix while implementing DiscoveryConfigChangeEvent. Usage event submission has retry behavior, but no way to dedupe if multiple event submissions end up going through for the same event. This adds an event_key to use for deduplication on the backend.

Manual Test Plan

Test Environment

Local build.

Test Cases

  • Check that event_key is filled when making prehog requests.

@charlestp charlestp added no-changelog Indicates that a PR does not require a changelog entry backport/branch/v18 labels Aug 12, 2026
@github-actions
github-actions Bot requested review from eriktate and jakealti August 12, 2026 18:33
@charlestp
charlestp force-pushed the charles/prehog-event-key branch from c36e2fc to 579692e Compare August 13, 2026 05:27
@charlestp
charlestp changed the base branch from master to charles/client-kind-user-agent August 13, 2026 05:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/branch/v18 no-changelog Indicates that a PR does not require a changelog entry size/sm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants