SpitfireLoad Testing & APMWhat's new

Business APM (business metrics and funnels)

You get business metrics from the span and log attributes your services already send: orders, payments, sign-ups, the amounts collected and what an error or a slowdown cost. Funnels show at which step users drop and the most common error at that step. Menu: APM → Business APM.

A business metric is a filter on APM data: a service's spans or log records are counted, or a numeric attribute such as order.amount is summed or averaged. The series is kept per minute; when a metric is added the last 24 hours are filled in. We suggest the amount of failed payments as the first metric: "yesterday's 40-minute error lost $4,000 of orders" gets a decision faster than a p95 chart.

Note

Business metrics hold no personal data. Attributes that look personal (e-mail, phone, user or customer id, IP, address) cannot be chosen; group values that look like e-mail addresses are counted under Hidden.

Add a business metric

  1. APM → Business APM › Add business metric, give it a Name (e.g. Orders).
  2. Source: Spans (traces) or Log records; pick the Service.
  3. For spans, the Endpoint (e.g. POST /orders; empty: all) and Records (All, Only successful, Only failed).
  4. Measure: Count, Sum or Average. For a sum or an average pick the Value attribute (numeric).
  5. For an amount, type the currency code in Unit (TRY, USD, EUR).
  6. Optionally add an attribute for Group by (payment.method, plan) and up to five Attribute filters. Save.

The card starts filling within a minute. Changing the source, the service, a filter or the measure starts a new series; changing the name or the unit does not.

Reading the dashboard

Click a card for the Records, Failed and Lost amount tiles with the change against the previous period. The Lost amount is an estimate: the amounts of failed records are added up, and a failed record without an amount counts as that minute's average. The Groups table shows the 20 largest groups, the rest as Others. Failed traces and Error logs open that service's failed records.

Add a funnel

  1. Add funnel › give it a Name (e.g. Checkout).
  2. Add 2 to 8 steps; each has a Type (Endpoint, Page or screen, Action), a service or app and a name (GET /cart, /cart, click Pay).
  3. Tie steps by: Trace (one request chain), Web/mobile session (the end-user SDK's session.id), Another attribute (e.g. order.id) or None (each step counted on its own).
  4. Within (min): how soon the steps must follow each other. Save.

The funnel card shows how many reached each step, the conversion, the drop, the Most common error and the p95 time.

Alert on a business metric

Press Add alert in the metric's detail. The measure can be the value, failed records, the lost amount, a drop against the previous window (%) or an anomaly against the same hour of earlier days. Set the thresholds, the Window and the channels, then Save. The rule runs every minute in the same engine as APM alerts and, when it fires, opens an event with the service's likely root cause.

Common problems

Symptom Cause Fix
The value attribute list is empty No numeric attribute was seen on the service's spans in the selected range Widen the time range or type the key.
"looks like personal data" The chosen key looks like an e-mail, a phone, a user id Pick another attribute (plan, payment.method, order.id).
Add business metric is disabled Free allows one definition (metric or funnel) Starter and up have no limit; License.
A funnel step is larger than the one before None is selected, the steps are counted on their own Tie the steps by trace, session or an attribute.

Related pages