Tracearr

Tracearr is a self-hosted monitoring dashboard for Plex, Jellyfin, and Emby servers that tracks live sessions, stream analytics, live television and music…

  • Media Applications
  • Media Servers
  • Monitoring & Logging
  • Tools & Utilities
Tracearr is a self-hosted monitoring dashboard for Plex, Jellyfin, and Emby servers that tracks live sessions, stream analytics, live television and music playback, geolocation, and account-sharing signals for administrators who need centralized usage review and real-time sharing alerts.

Platform availability

Available on 4 of 10 platforms

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

65/100 Good

Maintained
91last commit 19 days ago
Popular
3447 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
502 GB minimum RAM

Availability: platform listings confirmed today, links checked 2 days ago

GitHub stars
47
Open issues
0
Last commit
2026-11-02
Latest release
v0.6.1
License
GPL-3.0
Activity
rising

Checked 12 days ago - source: GitHub (Tracearr/Media-Server-SSE)

Resources & Compatibility

Minimum requirements: 2 GB RAM.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Generate the .env secrets first Before starting Tracearr, create a .env file with JWT_SECRET and COOKIE_SECRET using the provided openssl commands. These secrets protect logins and sessions; without them the app may not work safely or may fail to sign user data. source
  • Deploy with the included Docker Compose file Download the provided docker-compose.pg18.yml file and run docker compose -f docker-compose.pg18.yml up -d. This starts the app plus its Postgres database and Redis cache, which Tracearr needs to store data and run properly. source
  • Check logs if it won’t start If Tracearr seems broken, run docker logs tracearr, tracearr-postgres, and tracearr-redis to look for errors. This usually reveals missing database connections, bad secrets, or cache problems faster than guessing. source
  • External services Tracearr requires external TimescaleDB (PostgreSQL 15+) and Redis; use Tracearr Supervised for the all-in-one image. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How should I generate the required Tracearr secrets?

Create a .env file containing JWT_SECRET and COOKIE_SECRET using the provided openssl commands before starting the app. These secrets protect logins and sessions, and missing values can make the app unsafe or fail to sign user data.

What should I check if the container won't start?

Run docker logs tracearr, tracearr-postgres, and tracearr-redis to look for errors. This usually reveals missing database connections, bad secrets, or cache problems.

How do Jellyfin and Emby provide stream data to Tracearr?

Plex reports its own numbers, while Jellyfin and Emby report through the Tracearr SSE plugin.

Does the interactive stream map require external tile keys?

No, the vector basemap ships inside the container, so there are no tile keys or requests to a third-party tile service. You can give a server a location so local network plays show there too.

How does a merged identity's trust score work?

The trust score is the worst of the identity's active accounts, so merging duplicates does not hide a problem. You can merge by hand or use suggestions, and split them again if wrong.

Answers sourced from github.com, github.com

Community

Collected 49 days ago - public community threads