-
Notifications
You must be signed in to change notification settings - Fork 35
Bug 2034765: Expose glean telemetry dictionary in a standardized format #783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: enterprise-main
Are you sure you want to change the base?
Changes from all commits
d22fec7
f832746
ec4382e
5828c8c
7970d3d
452eb95
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| --- | ||
| loader: taskgraph.loader.transform:loader | ||
|
|
||
| transforms: | ||
| - gecko_taskgraph.transforms.job:transforms | ||
| - gecko_taskgraph.transforms.task:transforms | ||
|
|
||
| kind-dependencies: | ||
| - toolchain | ||
| - fetch | ||
|
|
||
| tasks: | ||
| semconv: | ||
| description: >- | ||
| Generate the resolved OTel semantic convention registry schema from | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same concerns on the description as above in kinds.rst |
||
| Firefox Glean metric definitions. The resulting resolved.yaml is | ||
| consumed by the `moa generate release` tool, which embeds it as a | ||
| semconv referrer artifact on Harbor. | ||
| run-on-projects: ["enterprise-firefox"] | ||
| run-on-repo-type: ["git"] | ||
| worker-type: b-linux | ||
| worker: | ||
| docker-image: {in-tree: "lint"} | ||
| max-run-time: 1800 | ||
| artifacts: | ||
| - type: file | ||
| name: public/build/resolved.yaml | ||
| path: /builds/worker/artifacts/resolved.yaml | ||
| - type: file | ||
| name: public/build/manifest.yaml | ||
| path: /builds/worker/artifacts/manifest.yaml | ||
| run: | ||
| using: mach | ||
| mach: "glean semconv --output-dir /builds/worker/artifacts" | ||
| use-caches: [checkout, pip, uv] | ||
| attributes: | ||
| shippable: true | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is this marked shippable? |
||
| shipping-phase: build | ||
| shipping-product: firefox-enterprise | ||
| index: | ||
| product: firefox | ||
| job-name: glean-semconv | ||
| type: shippable | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As above: why is this marked shippable? |
||
| treeherder: | ||
| symbol: Glean(semconv) | ||
| kind: build | ||
| platform: linux64/opt | ||
| tier: 1 | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to provide better context for what any of this means? I barely know what OTel means (using "OpenTelemetry" would be nicer), but would have no idea what a "resolved semantic convention registry schema" is nor what the
moa generate releasetool is or why we want to use themoa generate releasetool.Here's an attempt: