Jonathan Halliday
Jonathan Halliday
As a data platform engineer, I wish to: - have the logger generate a JSON schema for its output, so that e.g. a typesafe API can be generated for working...
https://issues.redhat.com/browse/WFLY-15421
First small step towards supporting the new experimental signal type for profiling! This PR introduces data interfaces corresponding to the OTLP model as defined in https://github.com/open-telemetry/oteps/pull/239 https://github.com/open-telemetry/opentelemetry-proto/pull/534 Until the latter...
Second step towards supporting the new experimental signal type for profiling... Following on from the interfaces in https://github.com/open-telemetry/opentelemetry-java/pull/6374 this adds the AutoValue generated implementation classes. Less to discuss here, it's...
The profiles.proto and pprofextended.proto formats use string values in various places, including 'location' (e.g. kernel, native, python, hotspot, php, ...), ValueType.unit (e.g. ["cpu","nanoseconds"], ["allocations","count"]", AttributeUnit.key and original_payload_format. To ensure consistency...
The marshaling utility code has not previously needed to support encoding of ByteBuffer type fields, as they are not used by any existing protocol. With the creation of the new...
Based on implementation experience with the draft version of the profiles spec, the use of lookup tables for storing values is space efficient but not particularly user friendly. This change...