Trask Stalnaker
Trask Stalnaker
hi @pichlermarc, a clarification PR sounds good!
@heyams I'm going to take over and finish this PR since you let me know offline you don't want to make the changes I've requested
status update, still need to: * add the `db.client.operation.duration` metric * add the `db.query.summary` attribute (requires updating the jflex sql parsing) * update `db.operation.name` and `db.collection.name` to only capture when...
hi @kaylareopelle @robbkidd! just checking what's the latest status of this PR? we are hoping to remove/archive the old semantic convention build tooling in the near-ish future, thanks!
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/versioning-and-stability.md makes several mentions of the API and SDK being separate components from a packaging / versioning / support guarantee perspective
If "Option C" is chosen in https://github.com/open-telemetry/semantic-conventions/issues/51#issuecomment-1561642471, I think that this reason not introducing the restriction will no longer be relevant: * allows dropping `.count` suffixes for more concise metric...
@reyang this issue is about namespaces for instrument names as opposed to namespaces for attribute names, did the TC vote also on this? thx
On second look, maybe the decision has been made(?), based on https://github.com/open-telemetry/semantic-conventions/issues/50#issuecomment-1564648535 > If "Option C" is chosen in https://github.com/open-telemetry/semantic-conventions/issues/51#issuecomment-1561642471, I think that this reason not introducing the restriction will...
Or, more precisely, https://github.com/open-telemetry/semantic-conventions/issues/51#issuecomment-1607892958 effectively decides the underlying question that led to this issue (naming of `system.processes.count` and `jvm.threads.count`) and so this specific issue is no longer blocking progress on...