commit | f4db1c7d8e431451218a4b7a40065eefd80a5f8e | [log] [tgz] |
---|---|---|
author | Robert Findley <rfindley@google.com> | Sun Mar 17 22:23:21 2024 -0400 |
committer | Robert Findley <rfindley@google.com> | Tue Mar 19 20:47:37 2024 +0000 |
tree | 85fb8205035d5485fcad7fce637dbf944b5cc7ab | |
parent | 0c295b22906383a241c53ab1e44d7b3160230c2c [diff] |
internal/graphconfig: rename to chartconfig, and display at /config This CL contains a few changes to improve the visibility and coherency of the "graph config": - rename to "chart config", since elsewhere we speak of telemetry.go.dev as hosting charts, and "graph" is an overloaded term - move the config.txt file into the chartconfig package, and expose it via embedding - display the chart config at the /config endpoint, since it is easier to read than the upload config - link to the current config in the overview of telemetry.go.dev Fixes golang/go#63418 Change-Id: Ia3cef815cb18b0b78f9f7c4d2e8fc82297e82f75 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/572335 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
This repository holds the Go Telemetry server code and libraries, used for hosting telemetry.go.dev and instrumenting Go toolchain programs with opt-in telemetry.
Warning: this repository is intended for use only in tools maintained by the Go team, including tools in the Go distribution and auxiliary tools like gopls or govulncheck. There are no compatibility guarantees for any of the packages here: public APIs will change in breaking ways as the telemetry integration is refined.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the time repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/telemetry:” in the subject line, so it is easy to find.
This repository uses eslint to format TS files, stylelint to format CSS files, and prettier to format TS, CSS, Markdown, and YAML files.
See the style guides:
It is encouraged that all TS and CSS code be run through formatters before submitting a change. However, it is not a strict requirement enforced by CI.
./npm install
./npm run all