Trask Stalnaker
Trask Stalnaker
Summarizing reasons for [not introducing this restriction](https://github.com/open-telemetry/opentelemetry-specification/pull/3477): * allows more flexibility in naming metrics, e.g. * allows dropping `.count` suffixes for more concise metric names, e.g. `system.processes` instead of `system.processes.count`...
Follow-up to #2175 cc @odubajDT
Sometimes there's a good reason not to follow existing guidance, but it can be hard to review semantic conventions without knowing this reasoning, or understanding the scope that the reasoning...
I think these might follow the _ vs . recommendation better if we name them: * `system.disk.io_time` -> `system.disk.io.time` * `system.disk.operation_time` -> `system.disk.operation.time` cc @open-telemetry/semconv-system-approvers
really need to fix this automation... ```suggestion schema_url: https://opentelemetry.io/schemas/1.33.0 ``` _Originally posted by @trask in https://github.com/open-telemetry/semantic-conventions/pull/2220#discussion_r2072069410_
https://github.com/lycheeverse/lychee/releases/tag/lychee-v0.19.0
Our current [bare metal self-hosted runners](https://github.com/open-telemetry/community/blob/main/assets.md#bare-metal-runners) are [going away](https://deploy.equinix.com/blog/sunsetting-equinix-metal/), so we are working on setting up a bare metal instance in Oracle Cloud as a GitHub self-hosted runner. So far...
I'd like to change the member base permission from "Read" (which gives all members read permission to all private repos) to "No permission" (which shouldn't affect anyone's ability to read...
Tracking follow-ups to https://github.com/open-telemetry/sig-security/issues/115 - [x] sig-end-user - [x] ~sig-mainframe~ archived - [x] sig-contributor-experience - [ ] sig-developer-experience - [x] sig-project-infra - [x] opentelemetry-specification - [x] opentelemetry-go-vanityurls - [ ]...
Tracking the GitHub missing features that are directly impacting OpenTelemetry. - [Support "Restrict who can push to matching branches" in Rulesets](https://github.com/orgs/community/discussions/61107#discussioncomment-6569780) - We use this extensively in classic branch protections...