Build a Plex Bandwidth and Data Usage Dashboard
Published 2026-10-16 · PlexBeam
A bandwidth and data usage dashboard gives you visibility into how your Plex server consumes network resources over time. Instead of checking the Plex UI during active streams, a dashboard shows historical trends, peak usage periods, per-user consumption, and alerts when bandwidth approaches your limits. This guide covers building a monitoring stack from free tools.
Dashboard Components
A complete Plex bandwidth dashboard combines three tools:
- Tautulli: Collects detailed stream data from Plex including bitrate, quality, transcode status, duration, and user information for every playback session.
- InfluxDB: A time-series database that stores metrics efficiently for long-term retention and fast queries.
- Grafana: A visualization platform that connects to InfluxDB and renders real-time and historical dashboards with customizable panels and alerting.
Tautulli alone provides basic history views, but exporting to InfluxDB and Grafana unlocks custom dashboards, cross-metric correlation, and sophisticated alerting rules.
Setting Up Tautulli
Tautulli is the data source. It connects to your Plex server and records every stream event:
- Deploy Tautulli as a Docker container or install it natively on your server.
- Connect it to your Plex server using the server URL and your Plex authentication token.
- Access the Tautulli web UI (default port 8181) to verify data collection is working.
- Let it run for at least 24 hours to accumulate enough data for meaningful dashboards.
Key Metrics Tautulli Collects
- Stream bitrate: The actual bitrate of each active stream including video, audio, and container overhead.
- Concurrent streams: How many streams are active simultaneously at any point in time.
- Total bandwidth: Combined bandwidth of all concurrent streams.
- Transcode vs direct play: Whether each stream is transcoded or played directly, and the transcode decision reason.
- Per-user data: Which users are streaming, what quality they receive, and how much data each session transfers.
- Duration and frequency: How long each session lasts and how often each user streams.
Exporting to InfluxDB
Tautulli can push data to InfluxDB through its notification system or through a custom script that queries the Tautulli API and writes to InfluxDB.
Script Approach
Create a script that polls the Tautulli API at regular intervals:
- Query the Tautulli API endpoint for current activity to get real-time stream data.
- Query the get_history endpoint for completed session summaries.
- Format the data as InfluxDB line protocol.
- Write to InfluxDB using its HTTP API.
- Schedule the script to run every 30-60 seconds for near-real-time data.
Data Points to Export
- Total concurrent streams (gauge metric, sampled every interval).
- Total bandwidth in Mbps (gauge metric).
- Per-user bandwidth (tagged by username).
- Transcode count vs direct play count.
- Data transferred per session (counter metric from completed sessions).
Building Grafana Dashboards
With data flowing into InfluxDB, build Grafana panels to visualize it:
Overview Dashboard
- Current streams panel: A stat panel showing the number of active streams right now.
- Current bandwidth panel: A gauge showing total bandwidth as a percentage of your upload capacity.
- Streams over time: A time series graph showing concurrent stream count over the past 24 hours, 7 days, and 30 days.
- Bandwidth over time: A time series graph showing total bandwidth consumption with your upload limit as a threshold line.
Per-User Dashboard
- Top users by data: A bar chart showing total data transferred per user over the selected time range.
- User activity heatmap: Shows when each user typically streams, helping identify peak usage patterns.
- Quality distribution per user: Pie charts showing each user's mix of direct play, 1080p transcode, 720p transcode, and other qualities.
Capacity Planning Dashboard
- Peak concurrent streams trend: Daily maximum concurrent streams plotted over weeks and months to show growth.
- Bandwidth headroom: How close peak usage gets to your upload limit, displayed as a percentage over time.
- Transcode load: CPU or GPU utilization during peak transcoding periods correlated with stream count.
Setting Up Alerts
Grafana supports alert rules that trigger notifications when conditions are met:
Bandwidth Alerts
- High bandwidth warning: Alert when total bandwidth exceeds 70% of your upload capacity for more than 5 minutes.
- Critical bandwidth: Alert when bandwidth exceeds 90% of capacity, indicating imminent quality degradation.
- Sustained high usage: Alert when average bandwidth over the past hour exceeds 60% of capacity, suggesting you may need to adjust quality limits or upgrade your plan.
Stream Alerts
- High concurrent streams: Alert when the number of simultaneous streams exceeds your comfortable limit.
- Excessive transcoding: Alert when more than 50% of active streams are transcoding, which may indicate client configuration issues.
Notification Channels
Grafana can send alerts through Discord, Slack, email, Telegram, PagerDuty, or webhook. Configure at least one channel so you receive alerts without having to watch the dashboard constantly.
Data Retention and Storage
Configure InfluxDB retention policies to manage storage:
- High-resolution data (30-second intervals): Keep for 7-14 days. This level of detail is useful for recent troubleshooting.
- Downsampled data (hourly averages): Keep for 6-12 months. Useful for trend analysis and capacity planning.
- Monthly summaries: Keep indefinitely for long-term growth tracking.
Use InfluxDB continuous queries or tasks to automatically downsample older data, reducing storage requirements while preserving trends.
Monthly Data Usage Tracking
If your ISP imposes data caps, track total data transfer:
- Sum all stream data transferred per month from Tautulli history.
- Display remaining data allowance as a Grafana panel.
- Set alerts when monthly usage approaches 80% and 90% of your cap.
- Compare upload data (remote streams) versus download data (media acquisition) to understand where your data budget goes.
Troubleshooting
Dashboard Shows No Data
- Verify the export script is running and not erroring. Check its logs.
- Confirm InfluxDB is accepting writes — query it directly to see if data points exist.
- Check Grafana's data source configuration — the InfluxDB URL, database name, and credentials must be correct.
Data Gaps in Graphs
- The export script may have stopped or crashed. Set up a process monitor to restart it automatically.
- InfluxDB may have been unreachable during some periods. Check InfluxDB logs for errors.
Alert Fatigue
- Tune alert thresholds based on your actual usage patterns. Start with generous thresholds and tighten them as you learn your normal ranges.
- Use alert grouping and cooldown periods to avoid repeated notifications for the same ongoing condition.