-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
2
-
Developer Tools
Hello guys,
As part of the Paper Plane initiative, we are looking to understand better the impact and usage of aggregation pipelines within the user's workflows.
We would like to add the property aggregation_id to the Compass telemetry that will serve as a unique identifier for aggregation pipelines so we track the journey. Ideally, we would like to populate this property in the following events:
-Aggregation Canceled
-Aggregation Copied
-Aggregation Deleted
-Aggregation Edited
-Aggregation Executed
-Aggregation Explained
-Aggregation Exported
-Aggregation Saved
Happy to discuss it further if you need more context