commit | 4b97e47acf65a2b73a1fa805be832b1b3fe83860 | [log] [tgz] |
---|---|---|
author | Hongxiang Jiang <hxjiang@golang.org> | Wed Jul 17 17:25:34 2024 +0000 |
committer | Hongxiang Jiang <hxjiang@golang.org> | Fri Jul 19 15:28:05 2024 +0000 |
tree | 63d11ff84aabf4f1646659a74cf1bd92b4b02c69 | |
parent | 79a4c46d39ef6377c67839b4767b7ee16343081e [diff] |
godev/cmd/worker: merging counters between start and end date data.parition() will generate a chart json (list of datums) based on the info stored in it's map. If /chart receive request only for one day (daily chart), data will only have one week key and the generated chart's datum: Week: That date. Key: The bucket name. Value: Counter for that date. If /chart receive request for multiple days (e.g. weekly chart), data will contain multiple week key. The generated chart's datum: Week: The end date. Key: The bucket name. Value: Sum of the counter for that bucket from START_DATE to END_DATE. Change-Id: Idf08ec87c40495e5624b1b2c713901ba63e687c8 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/599095 Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com> Reviewed-by: Robert Findley <rfindley@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.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