@lerix-dev/lerix-edge 0.2.0 or later. Both features use the
lerix client from Installation. For what you
see in the dashboard, read Analytics and
Feedback.
Analytics
- Events land in the same funnels and user counts as your apps’ events.
userIdis your own ID for the user, the same one your apps pass tosetUser(). - Names start with a letter, then letters, digits, spaces,
_,.,:or-(2 to 64 characters). Up to 25 properties, with string (up to 1,024 characters), finite number, boolean ornullvalues. An invalid name drops the event; an invalid property is dropped on its own.track()never throws.
Delivery
Events are buffered in the isolate (up to 1,000, oldest dropped first) and sent in batches of up to 100, after the response throughwaitUntil, or as soon as
50 are waiting. There is no timer, because isolates freeze between requests.
Outside wrap(), for example in a cron handler or a queue consumer, flush
before you return:
Environment and opt-out
Events carryplatform: "edge", the runtime as the OS, your app’s version and
build number, and the environment: the environment option, or NODE_ENV
where it can be read, with production sent as prod and development as
dev (prod when unset).
analytics: false in the Lerix.init options turns track() into a no-op.
Feedback
- Attachments are uploaded first, then the feedback is created with their IDs.
- Failed requests are retried twice with the same client ID, so a retry never duplicates the feedback.
submit()rejects withLerixApiException(INVALID_FEEDBACKfor input that can’t be sent, or the API’s error) and resolvesnullwithenabled: false.- Inside a traced request, the feedback links to the trace.
The
userId you pass is stored as reported by your server. Replies by push
only go to users verified through a client SDK’s setUser.