Log
Represents a combination of the event related data LogEventAction and the common recorder data parts.
Parameters
Product code, e.g. IU, TC, TB. Product code should contain uppercase latin letters only and be at least one symbol long.
Map from names of ids associated with the event to their values, e.g projectId, organisationId. All values from that map will be hashed twice on send and on receive. It should not be empty.
Flag is used to distinguish between internal and external users. E.g we may want to exclude company’s employees from logs, because they know much more about the product.
Unix time epoch of the time when the event occurred, in UTC.
Product build number. Could include numbers and dots.
In web applications, it is usually a web session. In desktop application, this is a UUID that connects all events from opening to closing the app.
Buckets are used to regulate the percentage of data that will be sent. The bucket number must belong to the interval of 0…255. It is usually calculated as a hash(device_id) % 256.
System data, recorded with each event and have common structure for all recorders.
Client data, recorded with each event and specific for certain recorder. For example, is_headless_mode for desktop applications started in headless mode. List of the fields should be discussed with Analytics Platform team first.