Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add some BuffferEventNumber or BufferTime before sent the events #643

Open
robertossan opened this issue Oct 4, 2023 · 2 comments
Open
Labels
type:enhancement New features or improvements to existing features.

Comments

@robertossan
Copy link

robertossan commented Oct 4, 2023

Is your feature request related to a problem? Please describe.
Right now, every time an event is tracked in the SnowPlow tracker, this event is saved in the Snowplow database and sent immediately, and there is no option to accumulate some events (25/50/100 events) or wait some time (30/60 seconds) before the sending occurs.
It would be interesting to have this functionality, to try to reduce the network traffic that is generated

Describe the solution you'd like
It should be nice if we have some fiiled on the EmitterConfiguration, like:

EmitterConfiguration().setBufferTimeout(<Int>)
EmitterConfiguration().setBufferEvents(<int>)

So, in that way, the emitter just emit every X seconds(sending the events on the database) or waiting until there are N events on the database, before emit the snowplow events.

Describe alternatives you've considered
We try to modify the BufferOption, but this is just working in case there are many events in the database for any other reason(e.g. if the network had been down), but not if has been required:

https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/mobile-trackers/configuring-how-events-are-sent/?platform=android#configuring-how-many-events-to-send-in-one-request

@robertossan robertossan added the type:enhancement New features or improvements to existing features. label Oct 4, 2023
@matus-tomlein
Copy link
Contributor

Thanks for the suggestion @robertossan! We plan to rework the batching mechanism for the v6 version of the tracker and we will keep this in mind.

@robertossan
Copy link
Author

robertossan commented Oct 16, 2023

Good to know @matus-tomlein ; thanks in advance.

Just to be informed, is there any release date for this v6?? or it's just something that will happens in some point in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement New features or improvements to existing features.
Projects
None yet
Development

No branches or pull requests

2 participants