How to measure a multi-step process using a duration meter

in some cases, customers want to meter different steps or phases of a complex process for example, a series of api calls may be used during a new user setup process and you would like to track how long each step takes at first glance, you may think you need separate meters for each api call or segment of the process, but there is a more efficient way to model this using dimensions create a single duration meter and create a dimension called 'segment' where the values each represent the different segments of the process when the process starts, the meter will send an event with value=1 and segment=firstsegment when the next segment begins, send another event (of the same meter) with value=1 and segment=nextsegment this process would continue until the final segment concludes, when a meter would be sent with value=0 and segment=lastsegment using this approach allows you to minimize the number of distinct meters to create and manage and still provides the same level of granular insight to the duration of each segment of the process as well as the total duration of the process from start to finish 📘 faqs and how tos docid\ bq14rede1rrwst00mbikx see related from metering and event ingestion how to track seat based objects in amberflo docid\ k8g0vmh6adgukb3dmezay how to meter the number of active seats or users for a customer docid\ vyzt7z7cdkrhjyl avl68 how to understand dimensions in amberflo docid\ ai7gyga p lhj8fwzca f how to verify the accuracy of meter data docid\ ne5rit1fjkfpatdbiej s how to track and bill for "high watermark" usage docid\ g l0lgdqyvfnccrsv2xbr how to handle erroneous or incorrect meters sent to amberflo docid\ awzcv2cw6swss2ffmcl58 how to find the meter id for retrieving and deleting a specific meter docid\ ty1vub6lz6u3fo nbfgb6 how to delete meters that are no longer in use docid\ x x7d16c6dwqrz zfdyvk how to handle high volume, high cardinality event streams docid\ edxld02jcxuqp2dkmd3 b