Requests, code and real users
See every request, from the browser to the database
Trace services with upstream OpenTelemetry SDKs or eBPF, profile CPU, watch database queries, and measure what real users and synthetic checks experience, in the same workspace as your infrastructure and network.
- OpenTelemetry
- eBPF on Linux
- Web · Android · iOS
6 products
Six ways to see your applications
No proprietary SDK: services, browsers and mobile apps send OpenTelemetry, and the collector adds what code cannot report.
APM and distributed tracing
Instrument services with upstream OpenTelemetry SDKs and agents, or capture request spans on Linux with no code changes using eBPF. See the service map, traces, grouped errors and deployments from CI/CD, Kubernetes rollouts and version changes, scoped by environment and service group.
- Upstream OpenTelemetry SDKs
- eBPF on Linux, kernel 5.8+
- GitHub · GitLab · Jenkins
Continuous profiling
The collector's eBPF profiler samples CPU across every process on a Linux host with no code changes, and pprof profiles can be scraped or pushed from other platforms. Explore flame graphs, top functions and stack traces across hosts or for one service, and compare them with the previous period.
- eBPF on Linux
- pprof scrape or push
Database monitoring
Collect health metrics from PostgreSQL, MySQL, SQL Server, Redis, MongoDB and Elasticsearch through the collector. For PostgreSQL, MySQL and SQL Server, see top queries, live query samples with wait events, explain plans and database load, and which traced services call each database.
- PostgreSQL · MySQL · SQL Server
- Redis · MongoDB · Elasticsearch
Real user monitoring
Instrument web, Android and iOS apps with upstream OpenTelemetry SDKs to see sessions, Core Web Vitals, errors and conversion funnels. Browser requests carry trace context into your backend traces, and optional web session replay records the page with inputs masked.
- Web · Android · iOS
- Core Web Vitals
- Web session replay
Synthetic monitoring
Schedule HTTP, DNS, TCP, TLS and ICMP checks from collectors you run, with an optional hop-by-hop network path on each run. Checks can also run from your workspace's own gateway collector, without ICMP or path tracing.
- HTTP · DNS · TCP · TLS · ICMP
- Hop-by-hop paths
Endpoint experience
Install the collector on the machines people work from to test the apps they use, such as Microsoft 365, Zoom or Salesforce, and trace the network path to each. Every endpoint gets an experience score and a likely bottleneck: Wi-Fi, gateway, network or the app itself, with Wi-Fi signal read on Linux.
- Apdex score
- App templates
One platform
Connected to the other areas
Application data links to the hosts, networks and alerts around it.
- InfrastructureA service's Infrastructure tab lists the pods, hosts, images and clusters it runs on, and a span opens the host's metrics, flame graph and logs.
- NetworkSynthetic checks and endpoint tests trace the hop-by-hop path to each app, with loss and round-trip time at every hop.
- SecurityThe software running inside each service, with runtime evidence and SBOM export, is on the service's Components tab.
- Operations & AIReady-made monitors cover latency, errors, faulty deploys and Core Web Vitals, and every SLO gets a burn-rate alert.
Send your first trace
Point an OpenTelemetry SDK at your workspace, or turn on eBPF instrumentation in the collector on Linux.