@wardx/core 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -140,6 +140,8 @@ Dropped items increment `wardx.internal.events_dropped` or `wardx.internal.logs_
|
|
|
140
140
|
|
|
141
141
|
Use counters and histograms for rates and latency. Use events for rare product facts: a purchase, an experiment exposure or goal, a named screen. Use logs for failures. Do not put user ids on metric dimensions.
|
|
142
142
|
|
|
143
|
+
A volume funnel is one event name and one counter per step. The engine does not join events by subject. See `docs/ARCHITECTURE.md`.
|
|
144
|
+
|
|
143
145
|
## Use case 3: Get Remote Config and assign an experiment
|
|
144
146
|
|
|
145
147
|
**When:** The server sends a config snapshot. You need a value for a subject.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wardx/core",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"description": "Runtime-agnostic Wardx engine for metrics, events, logs, Remote Config, and experiments.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"wardx",
|
|
@@ -36,4 +36,4 @@
|
|
|
36
36
|
"publishConfig": {
|
|
37
37
|
"access": "public"
|
|
38
38
|
}
|
|
39
|
-
}
|
|
39
|
+
}
|