Tracearr is a self-hosted monitoring platform for Plex, Jellyfin and Emby media servers. It puts every server you run behind one dashboard: live streams, per-server health, playback analytics across the whole catalogue, and a set of checks that surface the thing media-server admins actually care about — friends and family quietly sharing their logins.

Where the media servers themselves report almost nothing outside their own admin pages, Tracearr keeps the history: who watched what, when, from where and on which device, with geolocation and ASN attached to each session.

Key Features

• Multi-server dashboard — connect Plex, Jellyfin and Emby together and see active streams, server health and per-server CPU, memory and bandwidth charts on one page.
• Session history — a complete log of each stream with user, title, device, quality, and where it came from (city, continent, ASN, postal code).
• Stream analytics — transcoding versus direct play, bandwidth over time, codec and resolution breakdowns, and device compatibility scores.
• Identity merging — a person with a Plex account and a Jellyfin account becomes one identity, so their watch time and trust score are counted once; merges can be accepted, made by hand, or split again.
• Account-sharing detection — per-identity trust scores and alerts flag suspicious concurrent streams and impossible travel between locations.
• Automations — rules that fire on those events rather than leaving you to watch the dashboard.
• Map and library views — a live stream map plus one browsable catalogue spanning every connected server.

Why Use It

Running more than one media server usually means three admin UIs, three notions of a user, and no shared history. Tracearr normalises all of it into one Postgres-backed view, which makes questions like “who is hammering my upload tonight”, “is this the same person as last month’s Plex account” or “what actually transcodes here” answerable without stitching exports together. It is also the rare project in this space that treats account sharing as a first-class signal instead of an afterthought.

Use Cases

• Households and small groups running Plex alongside Jellyfin, wanting one traffic and usage picture.
• Admins who need proof — date, device, location — before confronting someone about a shared password.
• Choosing stream settings with data: see which clients transcode, and what that costs in bandwidth.
• Keeping a long-term viewing and bandwidth history without handing it to a third-party service.

Things to Know

Plex reports its own metrics; Jellyfin and Emby report theirs through the companion Media-Server-SSE plugin, which has to be installed on those servers. The project is active and frequent-release (2.x line), ships official iOS and Android companion apps, and keeps full documentation at docs.tracearr.com.

Requirements

The published container image ghcr.io/connorgallopo/tracearr running alongside its database and cache services from the documented compose stack — a PostgreSQL/TimescaleDB instance and Redis — plus network access to each media server it monitors.