jack-berg
jack-berg
The OTLP exporter builders have `addheader(String key, String value)` for adding static headers, but header based authentication often requires that the header value be refreshed over time. The OTLP exporter...
Resolves #2647. The simplest possible fix would have been to simply change `LogProcessor#emit` to accept `LogRecord` instead of `LogData`, but I took the opportunity to add some additional detail to...
Should there be a global accessor for LogEmitterProvider? In java (discussed [here](https://github.com/open-telemetry/opentelemetry-java/issues/4081)) we think the answer is no because the global accessor is reserved for API components (i.e. MeterProvider, TracerProvider)...
There's currently an inconsistency between [LogProcessor](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/logging-library-sdk.md#logprocessor) and the [SpanProcessor](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#span-processor) concept it was modeled after which severely limits the usefulness of LogProcessor. Multiple SpanProcessors can be registered on a TracerProvider, and...
The [spec](https://github.com/open-telemetry/opentelemetry-specification/blame/main/specification/metrics/data-model.md#L1400) says the following about the SDK prometheus exporter and resource attribute: > In SDK Prometheus (pull) exporters, resource attributes SHOULD be converted to the ["target" info](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#supporting-target-metadata-in-both-push-based-and-pull-based-systems) metric family;...
The metric semantic conventions has the following [instrument naming](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/metrics/semantic_conventions#instrument-naming) recommendation: > limit - an instrument that measures the constant, known total amount of something should be called entity.limit. For example,...
Instrument [units](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#instrument-unit) MUST be ASCII strings. Instrument [descriptions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#instrument-description) MUST support [BMP (Unicode Plane 0)](https://en.wikipedia.org/wiki/Plane_(Unicode)#Basic_Multilingual_Plane), which is basically only the first three bytes of UTF-8. Both of these allow [control characters](https://en.wikipedia.org/wiki/Control_character)...
**Describe the bug** [KafkaMetrics](https://github.com/micrometer-metrics/micrometer/blob/main/micrometer-core/src/main/java/io/micrometer/core/instrument/binder/kafka/KafkaMetrics.java#L252-L253) converts the metric `kafka.consumer.connection.count` to a counter despite the number of connections _not_ being monotonically increasing. This is causing issues in in the [opentelemetry micrometer shim](https://github.com/open-telemetry/opentelemetry-java/tree/main/micrometer1-shim),...
I recently wrote / published a blog post about otel exponential histograms on [New Relic's blog](https://newrelic.com/blog/best-practices/opentelemetry-histograms). Its only got 1 or 2 vendor specific references that are easy to remove,...
The spec [PR #2676](https://github.com/open-telemetry/opentelemetry-specification/pull/2676) to add a log API and the followup [PR #2768](https://github.com/open-telemetry/opentelemetry-specification/pull/2768) to align log API / SDK component naming impacts SDKs which have been prototyping the log...