Metrics
Configure a metric over an event type to aggregate the events over time and query the result as a time series. The metric accepts filters, dimensions and different calculation functions.
A metric answers questions about the aggregate behavior of the operation:
- the number of transactions processed per hour;
- the total approved amount per currency;
- the proportion of successful authentications;
- the number of refunds stuck in review for more than two days.
Transaction count over time. The drop detected at the end may trigger a monitor.
Where to configure
Under Settings > Event types, open the event type and go to the Metrics tab.
When creating a metric, choose what it observes:
- Aggregation: counts, sums or calculates percentages of events as they arrive. This is the type of metric used in most cases.
- Open tracking: follows how many entities remain held in each value of a trackable field and for how long.
The choice defines which measures the form offers. A metric cannot mix the two types: open measures and ordinary measures come from different mechanisms and require separate metrics.
Limits
- Maximum of 20 metrics per event type.
- Maximum of 10 dimensions per metric.
- Maximum of 2 trackable fields per event type.
- Two metrics of the same event type accept the same combination of dimensions. Metrics created before this version keep the previous requirement of a unique combination among themselves.
Retention periods per granularity are listed in limits and parameters.
Using metrics
- Monitors observe an aggregation of the metric at regular intervals and open alerts.
- Dashboards gather charts from several metrics on a single screen.
A metric in use by one or more monitors cannot be removed. The event type’s default metric, the one without dimensions, cannot be removed either.
Table of contents
- Components - dimensions, aggregations and filters that define the metric
- Tracking - time each entity spends in each value of a field
- Chart - granularity, series, filters and alert highlighting