James Tucker fe69b7f0e5 cmd/tailscale: add event bus queue depth debugging ...

Under extremely high load it appears we may have some retention issues
as a result of queue depth build up, but there is currently no direct
way to observe this. The scenario does not trigger the slow subscriber
log message, and the event stream debugging endpoint produces a
saturating volume of information.

Updates tailscale/corp#36904

Signed-off-by: James Tucker <james@tailscale.com>

2026-02-06 10:46:29 -08:00

..

cert.go

all: remove AUTHORS file and references to it

2026-01-23 15:49:45 -08:00

debug.go

cmd/tailscale: add event bus queue depth debugging

2026-02-06 10:46:29 -08:00

debugderp.go

all: remove AUTHORS file and references to it

2026-01-23 15:49:45 -08:00

disabled_stubs.go

all: remove AUTHORS file and references to it

2026-01-23 15:49:45 -08:00

localapi_drive.go

all: remove AUTHORS file and references to it

2026-01-23 15:49:45 -08:00

localapi_test.go

all: remove AUTHORS file and references to it

2026-01-23 15:49:45 -08:00

localapi.go

ipn/localapi: stop logging "broken pipe" errors (#18487)

2026-01-26 16:41:03 -08:00

pprof.go

all: remove AUTHORS file and references to it

2026-01-23 15:49:45 -08:00

serve.go

all: remove AUTHORS file and references to it

2026-01-23 15:49:45 -08:00

syspolicy_api.go

all: remove AUTHORS file and references to it

2026-01-23 15:49:45 -08:00

tailnetlock.go

all: remove AUTHORS file and references to it

2026-01-23 15:49:45 -08:00