commit | 79a4c46d39ef6377c67839b4767b7ee16343081e | [log] [tgz] |
---|---|---|
author | Hongxiang Jiang <hxjiang@golang.org> | Tue Jul 16 21:15:53 2024 +0000 |
committer | Hongxiang Jiang <hxjiang@golang.org> | Thu Jul 18 16:59:24 2024 +0000 |
tree | 7284e6619ab6f9fa4d24d89cecc609f41b9f55c9 | |
parent | 0b706e19b70189f217f242e6875dc0bb8e64b601 [diff] |
godev/cmd/worker: accept start and end query params for /chart 1. The /chart endpoint will either accept 'date' or both 'start' and 'end' query parameters. a using 'date' means the 'start' and 'end' are the same date. b 'date' can not be used same time as params 'start' or 'end'. 2. /chart only accept when both 'start' and 'end' are provided. 3. /chart will generate json following naming: a. DATE.json if the query param is the 'date' or 'start' == 'end' b. START_END.json other wise. Change-Id: Ia559ec8e149e4861dce469f5aceef036eea8aa60 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/598718 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