Skip to main content

Timing Performance

The Timing Performance page (/timings) gives you a detailed breakdown of latency data across your system. It is organized into three tabs: Categories, Touchpoints, and Explore.

Categories tab​

Categories group related touchpoints together (e.g. api/checkout groups api/checkout/submit, api/checkout/validate, etc.). The Categories view shows a table of all categories registered for your team, along with aggregate latency metrics.

Click any category row to open the Category Detail page, which shows:

  • Latency percentiles (p50, p95, p99) for the category as a whole
  • A breakdown of individual touchpoints within the category
  • A latency chart over time

Touchpoints tab​

The Touchpoints view lists every individual touchpoint registered for your team. A touchpoint is the most granular unit of measurement — it corresponds to a specific operation you instrument in your code (e.g. db/query/user-by-id).

Click any touchpoint row to open the Touchpoint Detail page, which shows:

  • Latency percentiles and a trend chart
  • Individual timing datapoints you can inspect
  • A comparison view to overlay this touchpoint against others

Unregistered touchpoints​

When SimpleLogs receives a timing event for a touchpoint name that hasn't been created in Settings yet, it tracks it as an unregistered touchpoint. These appear in the Touchpoints list with a distinct indicator. You can register them from this view or from Settings → Touchpoints.

Explore tab​

The Explore tab is a free-form latency explorer. Use it to query timing data without being constrained to a pre-defined touchpoint or category. This is useful for ad-hoc investigation when you know the approximate name of an operation but haven't formally registered it yet.

Adding timing data​

Timing data is sent via the SDK or the REST API using start / end pairs or pre-computed duration values. See the Client SDK — Server Logging and Client SDK — Client Logging guides for usage examples.