Skip to main content

Settings — Touchpoints

The Touchpoints tab in Settings is where you register, organize, and manage the named measurement points in your application.

What is a touchpoint?​

A touchpoint is a named operation you want to measure — for example api/users/login, db/query/products, or worker/email/send. You attach a touchpoint name when you call logger.log(), logger.start(), or logger.end() in your code, and SimpleLogs uses that name to group and analyze your data.

Touchpoints can be nested into a category tree for organization. For example, the touchpoints api/checkout/submit and api/checkout/validate both belong to the api/checkout category.

Registering a touchpoint​

You can register touchpoints in two ways:

  1. Proactively — Create them in Settings before you instrument your code
  2. Reactively — Send timing data with a new touchpoint name and register it from the Timing Performance → Touchpoints page when it appears as unregistered

Touchpoint tree​

Registered touchpoints are displayed as a hierarchical tree organized by category. You can:

  • Create a category — A top-level grouping node (e.g. api/checkout)
  • Create a touchpoint — A leaf node within a category that receives timing data
  • Edit a touchpoint — Rename or re-categorize it
  • Delete a touchpoint — Removes the touchpoint and stops associating new data with it (historical data is preserved)

Unregistered touchpoints​

When your code sends a timing event to SimpleLogs using a touchpoint name that hasn't been registered, SimpleLogs still stores the data and marks the touchpoint as unregistered. These appear in the Timing Performance view with a distinct indicator.

Registering an unregistered touchpoint associates all its historical data with the registered entry — no data is lost.

Why register touchpoints?​

Registered touchpoints unlock:

  • Category-level aggregation on the Timing Performance page
  • Named entries in the Dashboard graph picker
  • Proper tree organization in the Log Explorer's grouped view