The Tracker object is responsible for co-ordinating the saving and sending of events as well as managing the optional Session object.
|The Emitter object you create||Yes||Null|
|The Subject that defines a user||No||Null|
|The Session object you create||No||Null|
|The name of the tracker instance||No||Null|
|The application ID||No||Null|
|If we base 64 encode json values||No||True|
|If loading into storage is done in sync||No||True|
|Function to get the desktop context||No||Null|
|Function to get the mobile context||No||Null|
|Function to get the geo-location context||No||Null|
|The logger to use within the application||No||Null|
A full Tracker construction should look like the following:
var logger = new ConsoleLogger(); var endpoint = new SnowplowHttpCollectorEndpoint(emitterUri, method: method, port: port, protocol: protocol, l: logger); var storage = new LiteDBStorage("events.db"); var queue = new PersistentBlockingQueue(storage, new PayloadToJsonString()); var emitter = new AsyncEmitter(endpoint, queue, l: logger); var subject = new Subject().SetPlatform(Platform.Mob).SetLang("EN"); var session = new ClientSession("client_session.dict", l: logger); Tracker.Tracker.Instance.Start(emitter: emitter, subject: subject, clientSession: session, trackerNamespace: "some namespace", appId: "some appid", encodeBase64: true, l: logger);
Tracker.Stop() methods take full responsibility for starting and stopping the threads required for processing everything asynchronously. Do not use any other
Stop functions other than the ones directly for the Tracker to prevent unknown behaviours.
LiteDBStorage object must be disposed of manually after stopping the Tracker so you will need to maintain a reference to this object.
Subject variables can all be altered directly from the Tracker via replicated setter methods.
The Tracker contains several critical functions that must be used to start Tracking.
This function must be called before any events will start being stored or sent. This is due to the fact that we do not want to start any background processing from the constructors so it is left up to the developer to choose when to start everything up.
If you attempt to access the Tracker singleton before Starting it an exception will be thrown.
- Starts the background emitter thread
- Starts the background session check timer (Optional)
Once this is run everything should be in place for asynchronous event tracking.
If you need to halt the Tracker from tracking events you can run this function. This will bring all event processing, sending and collection to a halt and nothing will be started again until
Start(...) is fired again.
WARNING: If you are using Client Sessionization stopping and then restarting the Tracker will result in the session index incrementing.
This is the function used for Tracking all events.