Trask Stalnaker
Trask Stalnaker
I only just found that the way I've been registering log processors via AutoConfigurationCustomizer is seriously flawed, and worried other people may be doing the same: ``` AutoConfigurationCustomizer.addLoggerProviderCustomizer( (builder, otelConfig)...
### Is your feature request related to a problem? Please describe. Currently none of the instrumentations emit schema url, which makes it harder for backends to detect which version of...
> I guess we should then consider doing the same for messaging ([`messaging.message.body.size` and `messaging.message.envelope.size`](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/messaging/messaging-spans.md#messaging-attributes)) and RPC ([`message.compressed_size` and `message.uncompressed_size`](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/rpc/rpc-spans.md#events))? _Originally posted by @pyohannes in https://github.com/open-telemetry/semantic-conventions/issues/460#issuecomment-1784814530_
### Area(s) area:db ### Is your change request related to a problem? Please describe. Cover both spans and metrics in database vendor specific pages. Currently they only mention spans. ###...
Vendor-specific database attributes that are also used in metrics should be moved out of `database/spans.yaml`, e.g. https://github.com/open-telemetry/semantic-conventions/blob/b780f480e73ffc2d1da117689475b7b9c8af610b/model/database/spans.yaml#L88-L103
This repository would exists to document common repository practices used across OpenTelemetry, with a couple of goals in mind: * to help maintainers to discover new practices which are working...
### Affected Repository https://github.com/open-telemetry/people ### Requested changes Create a new repository named "people". ### Purpose This repository will be used for IaC management of org membership using [CLOWarden](https://github.com/cncf/clowarden). Related to...
Just copy pasted over from the (to be previous) Event API as a first pass...
Resolves https://github.com/Azure/azure-sdk-for-java/issues/34128
Restore missing diagnostic logging that was lost in #41106