You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
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
The text was updated successfully, but these errors were encountered: