Brad Fitzpatrick af4b7b0363 tsweb/varz: add goamd64_capable and goamd64_compiled default metrics ...

To decide whether we can bump GOAMD64 for our production binaries, we
first need to know what x86-64 microarchitecture levels the fleet's
CPUs actually support. Add two gauges to the default metric set on
linux/amd64: goamd64_capable, the maximum GOAMD64 level the host CPU
supports per /proc/cpuinfo, and goamd64_compiled, the level the
running binary was built with per its build info. Both are computed
once at init and report 0 on error.

The per-level feature lists match the checks in Go's
runtime/asm_amd64.s.

Updates tailscale/corp#47099

Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>
Change-Id: I3b4e5431ae1501f0b7d584c12d9af805e9ab6125

2026-08-25 07:23:04 -07:00

..

promvarz

all: remove AUTHORS file and references to it

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

varz

tsweb/varz: add goamd64_capable and goamd64_compiled default metrics

2026-08-25 07:23:04 -07:00

debug_test.go

tsweb: add TS_DEBUG_TRUSTED_CIDRS envknob to debug (#19283)

2026-04-08 18:47:52 -04:00

debug.go

all: remove AUTHORS file and references to it

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

log.go

all: remove AUTHORS file and references to it

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

pprof_default.go

all: remove AUTHORS file and references to it

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

pprof_js.go

all: remove AUTHORS file and references to it

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

request_id.go

cmd/tailscale/cli: fix time in tailscale routecheck (#19956)

2026-06-01 16:12:08 -07:00

tsweb_test.go

cmd/vet: add subtestnames analyzer; fix all existing violations

2026-04-05 15:52:51 -07:00

tsweb.go

all: apply go fix

2026-07-10 17:39:16 -07:00