Know how your Stellar app is used, without profiling the people using it.
Shared analytics for Stellar projects: API metrics over OpenTelemetry, web analytics, and a wallet funnel. Every number carries its definition, and the operator view only ever sees aggregates.
Signing in uses a one-time wallet signature. No transaction is sent.
7963980
03:30 PM–05:30 PM · worst bucket 12.9% 5xx
Sample project · Overview
Synthetic sample data. Not a real project.
- RequestsTotal HTTP responses counted by your exporter in the selected range.
- 36,10913% versus the previous period
- p50 latencyThe median response time, interpolated from merged fixed-boundary histograms. An approximation.
- 48ms5.9% versus the previous period
- p95 latency95% of responses were faster than this. Interpolated from merged histograms, so approximate.
- 318ms21% versus the previous period
- p99 latency99% of responses were faster than this. Responses beyond the top bucket report its lower bound, 10 s.
- 702ms1.7% versus the previous period
- Server errors5xx responses divided by all responses in the range. Deltas are in percentage points.
- 1.4%1.0 pt versus the previous period
31,840 previously · Compared with the equal period before
51ms previously · Median
262ms previously · Approximate
690ms previously · Approximate
0.4% previously · 5xx ÷ all
Status classes
- 2xx Success
34,210
94.7% of responses
- 3xx Redirect
612
1.7% of responses
- 4xx Client error
780
2.2% of responses
- 5xx Server error
507
1.4% of responses
| Method | Route | Requests | p95 | 5xx | Trend |
|---|---|---|---|---|---|
| GET | /v1/pools | 18,420 | 142 | 0.2% | |
| POST | /v1/quote | 9,310 | 318 | 3.1% | |
| GET | /v1/pools/:id | 6,204 | 96 | 0.1% | |
| POST | /v1/swap/submit | 2,175 | 640 | 1.2% |
Three signals, each with its limits stated
- API metrics
- Requests, latency percentiles and error rates per route, from the OpenTelemetry metrics your services already emit. Metrics only; traces and logs are rejected.
- Percentiles are approximations from merged histograms.
- Web analytics
- Page views, referrers and devices from a pinned, self-hosted Umami, issued only after you verify the domain by DNS or a file.
- Visitor counts follow Umami's definitions.
- Wallet funnel
- Where people drop between connecting a wallet and submitting a transaction, counted from event names alone.
- Reported by your frontend. It cannot prove a ledger outcome.
From sign-in to first data point
- 1Sign in with your wallet. A one-time signature on testnet. No email, no password.
- 2Create a project and an ingest key. The key, never the payload, decides which project a metric belongs to.
- 3Dual-export from your service. Keep your existing APM and add Pulse as a second OTLP/HTTP JSON destination.
- 4Watch the overview fill in. It refreshes every 15 seconds, with routes, latency and error rate side by side.
Environment
export OTEL_EXPORTER_OTLP_METRICS_PROTOCOL=http/json export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=https://<your-pulse-host>/v1/metrics export OTEL_EXPORTER_OTLP_METRICS_HEADERS="Authorization=Bearer <ingest key>" export OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=delta
Privacy by omission: no IPs, request bodies or wallet addresses in analytics
What Pulse stores
- Counters and latency histograms per route, per minute.
- Wallet event names and counts.
- A one-way hash of each ingest key secret.
- Project membership, by Stellar public key, for access control.
What Pulse does not store
- Traces, spans, logs or request bodies.
- IP addresses in Pulse's own tables. Web analytics run on Umami, which has its own data handling.
- Wallet addresses, signatures or transaction XDR in analytics.
- Anything that would let one project read another's data. Isolation is enforced in the database, not only in the app.
Definitions you can check
- Server error rate
- 5xx responses divided by all responses, over the selected range.
- Latency percentiles
- Interpolated from merged fixed-boundary histograms. They are approximations, and the top bucket reports its lower bound (10 s).
- Wallet events
- Reported by your frontend through the tracker. They are not confirmed on the Stellar ledger.