Meter with Filtering Rule
A 3-step recipe with Amberflo. We can help you get access.
Recipe · 3 steps
Meter with Filtering Rule
with Amberflo
Create a meter, add a filtering rule, then ingest a matching event.
- Create the meter definition with the supplied dimension declared.
- Register a filtering rule that includes events matching the dimension value.
- Ingest an event carrying the filtered dimension so the rule is exercised.
What you'll need to have ready
- apiKey: Amberflo API key supplied in the X-API-KEY header.
- meterApiName: Unique API name for the meter.
- displayName: Human-readable display name for the meter.
- type: Aggregation type (SUM_OF_ALL_USAGE, MAX_IN_PERIOD, UNIQUE_CUSTOMERS_COUNT).
- dimensionName: The dimension the filtering rule applies to (e.g. region).
- dimensionValue: The dimension value to include or exclude.
- customerId: Customer the ingested event is attributed to.
- meterValue: The usage amount for the ingested event.
- meterTimeInMillis: Event timestamp in Unix milliseconds.
For your developer
Arazzo workflow amberflo:meter-with-filtering-rule, 3 operations: createMeterDefinition → createFilteringRule → ingestMeterEvents. Specs on APIs.io.