How to handle erroneous or incorrect meters sent to Amberflo

how to handle erroneous or incorrect meters sent to amberflo amberflo provides an easy to use api that you can invoke to cancel a single usage event or a large set of events the system will also take care of propagating the changes to the usage aggregations as well as to the invoicing or rewards payment systems if those are affected by the cancellation you have the option to manually filter and remove meter events based on different properties (such as the ingestion time, or more granular like specific dimension values) see our docs for more information meter corrections (undo events) docid\ hembk9u0jbqobr3lhsi n there are two categories of issues causing incorrect meter data to be sent to amberflo system wide issues these are caused by data problems or bugs in the account system responsible for sending events to amberflo for example, a misconfiguration at the event source on 1/1 may cause all events to be ingested in an incorrect format this error is noticed on 1/8, so the customer wants to delete all erroneous meters sent between 1/1 and 1/8, and resend the correct meters after resolving the bug incorrect single events, usually caused by unintentional or unsuccessful usage of some resource in this case, you don't want to bill the customer for something they did not intend to use (or were unable to access), so you want to cancel any events that correspond to this unsuccessful usage to delete erroneous meters in bulk (in the case of a system error), amberflo exposes a 'filering rules' api this api allows you to define rules for filtering out and removing sets of previously ingested meter events https //app amberflo io/ingest snapshot/custom filtering rules https //app amberflo io/ingest snapshot/custom filtering rules to cancel individual events, such as from unsuccessful usage, you can use the filtering mechanism described above to remove events by their 'unique id' if you do not know the 'unique id' or have reused it for another record, you can provide certain 'resource related properties' as an alternative method these properties allow the system to identify the resource which was erroneously accessed to cancel an individual event for a given resource, just send an ingest event that includes the relevent 'resource related properties' and the following dimension "aflo cancel previous resource event" with "true" set as its value 📘 faqs and how tos docid\ bq14rede1rrwst00mbikx see related from metering and event ingestion how to measure a multi step process using a duration meter docid\ jejnqgjekdtlycfyxzsjj 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 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