This document aims to address the common as well as not-so-common queries and issues you might encounter while using the RudderStack platform.
This section contains some commonly-asked questions about the RudderStack Server.
Yes, you are right. We don't explicitly list out any server-side sources, though all sources are pretty much the same. When you create a source, you get a
writeKey which you can use to send events to RudderStack Data Plane. The
We recommend using well-tested GitHub releases. Upgrading the RudderStack Server to v0.1.6 should not be a problem.
This section aims to address the commonly asked questions about RudderStack's Transformation feature.
The batching is done on a per end-user level. All the events from a given end-user are batched and then sent to the transformation function. The batching process is controlled via the following three parameters in
processSessions = False (make it
True for batching)
sessionThresholdEvents = 100
sessionInactivityThresholdInS = 120
Events from an end-user are batched till we have 100 events or 120 seconds of inactivity since the last event. This list is then passed to the transformation function.
There is parallelism in calling the transformation function, so ideally it should not slow the system. However, if you have a really slow transformation, you can increase the number of transformation workers by tweaking
Number of user events that are batched together can be configured with
sessionInactivityThresholdInS. Higher the numbers, longer the events are grouped into a session. It is important to note that these will increase the memory footprint proportionally.
Each execution of a transformation happens in a sandboxed V8 isolate. We do not support sharing data or connections across executions.