ServiceLink EXOS | Analytics

One script tag

Add EXOS Analytics to your app

Session replay, traces, and events will appear within seconds.

2. Paste this before </head>
3. Track product events (recommended)

Name your events after what users do, not what the server does. This makes funnels, retention, and paths immediately useful. 

// Frontend: track user actions
window.HyperDX.addAction('order.created', {
  orderId: order.id,
  value: order.total,
});

// Identify users (enables cross-session analytics)
window.HyperDX.setGlobalAttributes({
  'user.id': user.id,
  'user.email': user.email,
  'user.role': user.role,
});
Open my workspace Data appears within seconds of the first page load.

How it works

1

The HyperDX browser SDK captures DOM snapshots, console logs, network requests, and user interactions.

2

Events stream to the analytics collector at collector.exos-demo.com.

3

Everything lands in the analytics store. Browse sessions, run queries, or explore events from this portal.

Next steps

Concepts & Data Model

The OpenTelemetry model, properties (by ServiceName), and the core tables.

API & Query Reference

Per-endpoint reference for the /api/* surface, with parameters and examples.

Access & Auth

Firebase sign-in (Microsoft / Google) and the read-only demo access mode.

Two ways in

The portal is gated by Firebase Authentication (sign in with Microsoft or Google). For evaluation and test automation, appending ?skipauth=true to any URL bypasses the front-end sign-in overlay.

Demo mode reaches the same isolated demo dataset and nothing more: every query runs as the least-privilege exos_readonly user, scoped to the default and exos databases only. See Access & Auth for how isolation is enforced.