TailscaleMetrictailscale.bytes.received.total
Total bytes receivedDimensions:None
Summary
Cumulative count of bytes received across all Tailscale network connections since daemon startup. This counter monotonically increases and resets only on process restart. Rising receive rates indicate active inbound traffic flow, while asymmetric patterns (compared to bytes sent) may signal one-way data transfers or routing issues. Essential for tracking overall network consumption and identifying bandwidth anomalies.
Interface Metrics (3)
Prometheus
Dimensions:None
Google Cloud MonitoringDimensions:None
Sources
Technical Annotations (9)
CLI Commands (1)
tailscale metrics printdiagnosticTechnical References (8)
exit nodecomponentDERP relaycomponentsubnet routercomponenttailnet policy filecomponentTailscale access controlcomponentDERP relay serverscomponentNAT traversalconceptnetwork flow logscomponentRelated Insights (6)
Exit node resource exhaustion from excessive inbound connections degrades performancewarning
▸
Tailscale client metrics available for Prometheus scrapinginfo
▸
High packet drop rate from ACL blocking indicates misconfigured access controlswarning
▸
DERP relay usage indicates direct connectivity failure between peerswarning
▸
Excessive traffic through exit node indicating performance bottleneckwarning
When a large volume of traffic is routed through a single exit node, it can create a performance bottleneck, saturating the exit node's bandwidth, CPU, or network interfaces. This degrades performance for all users routing through that exit node and creates a single point of failure.
▸
Network flow logs now include node information automaticallyinfo
▸