feat(e2e-shared): add event status tracking and connection indicators#1281
Draft
abueide wants to merge 1 commit into
Draft
feat(e2e-shared): add event status tracking and connection indicators#1281abueide wants to merge 1 commit into
abueide wants to merge 1 commit into
Conversation
Events now have three states: queued (orange), sent (green), failed (red) instead of just sent/unsent. The Logger tracks HTTP status codes per event. Connection status: green when events post successfully, orange when server responds with an error (e.g. 401), red when server is unreachable. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds proper event status tracking to the example app. Events now show whether they were successfully sent, are pending, or failed — with HTTP status codes displayed per event.
Changes
ErrorType.EventsDroppedinstead of blindly marking all as sent after flushWhy
Previously all events were marked green after flush regardless of whether the server accepted or rejected them. With an invalid write key, events would show as "sent" even though they were dropped with a 401. This makes it possible to visually verify the SDK's error handling behavior.
🤖 Generated with Claude Code