From a56dc4a2124e3abb50941dd94a497566e96b9127 Mon Sep 17 00:00:00 2001 From: jcj46548-ux Date: Mon, 11 May 2026 19:09:04 +0800 Subject: [PATCH] docs: update Go documentation links Signed-off-by: jcj46548-ux --- CONTRIBUTING.md | 2 +- README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8780b12adf..46f65e80c6 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -12,7 +12,7 @@ Prometheus uses GitHub to manage reviews of pull requests. of inspiration. * Relevant coding style guidelines are the [Go Code Review - Comments](https://code.google.com/p/go-wiki/wiki/CodeReviewComments) + Comments](https://go.dev/wiki/CodeReviewComments) and the _Formatting and style_ section of Peter Bourgon's [Go: Best Practices for Production Environments](http://peter.bourgon.org/go-in-production/#formatting-and-style). diff --git a/README.md b/README.md index 3b8c2d811e..b085528111 100644 --- a/README.md +++ b/README.md @@ -247,7 +247,7 @@ perf_event_open`](http://man7.org/linux/man-pages/man2/perf_event_open.2.html). By default, the `perf` collector will only collect metrics of the CPUs that `node_exporter` is running on (ie -[`runtime.NumCPU`](https://golang.org/pkg/runtime/#NumCPU). If this is +[`runtime.NumCPU`](https://pkg.go.dev/runtime#NumCPU). If this is insufficient (e.g. if you run `node_exporter` with its CPU affinity set to specific CPUs), you can specify a list of alternate CPUs by using the `--collector.perf.cpus` flag. For example, to collect metrics on CPUs 2-6, you @@ -366,7 +366,7 @@ This can be useful for having different Prometheus servers collect specific metr Prerequisites: -* [Go compiler](https://golang.org/dl/) +* [Go compiler](https://go.dev/dl/) * RHEL/CentOS: `glibc-static` package. Building: