Skip to content

Conversation

@eli-darkly
Copy link
Contributor

[6.0.0] - 2018-05-10

Changed:

  • To reduce the network bandwidth used for analytics events, feature request events are now sent as counters rather than individual events, and user details are now sent only at intervals rather than in each event. These behaviors can be modified through the LaunchDarkly UI and with the new configuration option inline_users_in_events. For more details, see Analytics Data Stream Reference.
  • The analytics event processor now flushes events at a configurable interval defaulting to 5 seconds, like the other SDKs (previously it flushed if no events had been posted for 5 seconds, or if events exceeded a configurable number). This interval is set by the new Config property flush_interval.

Removed:

  • Python 2.6 is no longer supported.
  • Removed the Config property events_upload_max_batch_size, which is no longer relevant in the new event flushing logic (see above).

…ue; fix tests to avoid making real connections
# Conflicts:
#	testing/test_ldclient.py
eli-darkly and others added 25 commits April 3, 2018 21:40
set schema header in event payload
re-add redundant key property in identify event
send as much of a feature event as possible even if user is invalid
include variation index in events and bump schema version to 3
@eli-darkly eli-darkly requested a review from ashanbrown May 10, 2018 22:03
@eli-darkly eli-darkly merged commit 7a0c80e into master May 11, 2018
@eli-darkly eli-darkly deleted the 6.0.0 branch May 11, 2018 00:20
eli-darkly added a commit that referenced this pull request Jan 31, 2019
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