Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added
NewExportPipeline
andInstallNewPipeline
, setup and install the exporter in tracing and metrics pipelines. (add NewExportPipeline and InstallNewPipeline for otlp #1373)OTEL_EXPORTER_JAEGER_AGENT_HOST
,OTEL_EXPORTER_JAEGER_AGENT_PORT
These environment variables can be used to override Jaeger agent hostname and port (Update Jaeger environment variables #1752)
ExportTimeout
was added to batch span processor. (AddExportTimeout
option to batch span processor #1755)trace.TraceFlags
is now a defined type overbyte
andWithSampled(bool) TraceFlags
andIsSampled() bool
methods have been added to it. (Make TraceFlags spec-compliant #1770)Event
andLink
struct types from thego.opentelemetry.io/otel
package now include aDroppedAttributeCount
field to record the number of attributes that were not recorded due to configured limits being reached. (Record links/events attribute drops independently #1771)OnEnd
andForceFlush
postShutdown
. (Add test to check bsp ignoresOnEnd
andForceFlush
post Shutdown` #1772)OTEL_RESOURCE_ATTRIBUTES
environment variable and merge them with theresource.Default
resource as well as resources provided to theTracerProvider
and metricController
. (Fix default merging of resource attributes from environment variable #1785)WithOSType
resource configuration option to set OS (Operating System) type resource attribute (os.type
). (OS and Process resource detectors #1788)WithProcess*
resource configuration options to set Process resource attributes. (OS and Process resource detectors #1788)process.pid
process.executable.name
process.executable.path
process.command_args
process.owner
process.runtime.name
process.runtime.version
process.runtime.description
k8s.node.name
andk8s.node.uid
attribute keys to thesemconv
package. (Add k8s.node.name and k8s.node.uid to semconv #1789)OTEL_EXPORTER_OTLP_ENDPOINT
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
OTEL_EXPORTER_OTLP_HEADERS
OTEL_EXPORTER_OTLP_TRACES_HEADERS
OTEL_EXPORTER_OTLP_METRICS_HEADERS
OTEL_EXPORTER_OTLP_COMPRESSION
OTEL_EXPORTER_OTLP_TRACES_COMPRESSION
OTEL_EXPORTER_OTLP_METRICS_COMPRESSION
OTEL_EXPORTER_OTLP_TIMEOUT
OTEL_EXPORTER_OTLP_TRACES_TIMEOUT
OTEL_EXPORTER_OTLP_METRICS_TIMEOUT
OTEL_EXPORTER_OTLP_CERTIFICATE
OTEL_EXPORTER_OTLP_TRACES_CERTIFICATE
OTEL_EXPORTER_OTLP_METRICS_CERTIFICATE
otlpgrpc.WithTimeout
option for configuring timeout to the otlp/gRPC exporter. (Adds support for timeout on the otlp/gRPC exporter #1821)Fixed
Span.IsRecording
implementation fromgo.opentelemetry.io/otel/sdk/trace
always returns false when not being sampled. (Fix span IsRecording when not sampling #1750)This means it uses the correct tag keys (
"otel.status_code"
,"otel.status_description"
) and does not set the status message as a tag unless it is set on the span. (Fix Jaeger span status reporting and unify tag keys #1761)"event"
key for a tag.Additionally, this tag is overridden, as specified in the OTel specification, if the event contains an attribute with that key. (Update precedence of event name in Jaeger exporter #1768)
Changed
RecordError
now records anexception
event to comply with the semantic convention specification. (Adds semantic conventions for exceptions #1492)go.opentelemetry.io/proto/otlp
. (Migrate to using go.opentelemetry.io/proto/otlp #1713)github.com/gogo/protobuf
togoogle.golang.org/protobuf
to matchgo.opentelemetry.io/proto/otlp
. (Migrate to using go.opentelemetry.io/proto/otlp #1713)context.Context
using its SpanContext is unified to store just the current Span.The Span's SpanContext can now self-identify as being remote or not.
This means that
"go.opentelemetry.io/otel/trace".ContextWithRemoteSpanContext
will now overwrite any existing current Span, not just existing remote Spans, and make it the current Span in acontext.Context
. (Store current Span instead of local and remote SpanContext in context.Context #1731)"go.opentelemetry.io/otel/export/trace".SpanSnapshot
is unified in a newParent
field.The existing
ParentSpanID
andHasRemoteParent
fields are removed in favor of this. (Update SpanSnapshot to use parent SpanContext #1748)ParentContext
field of the"go.opentelemetry.io/otel/sdk/trace".SamplingParameters
is updated to hold acontext.Context
containing the parent span.This changes it to make
SamplingParameters
conform with the OpenTelemetry specification. (Update SamplingParameters #1749)JAEGER_ENDPOINT
,JAEGER_USER
,JAEGER_PASSWORD
to
OTEL_EXPORTER_JAEGER_ENDPOINT
,OTEL_EXPORTER_JAEGER_USER
,OTEL_EXPORTER_JAEGER_PASSWORD
in compliance with OTel spec (Update Jaeger environment variables #1752)
BatchSpanProcessor.ForceFlush
to abort after timeout/cancellation. (Modify ForceFlush to abort after timeout/cancellation #1757)DroppedAttributeCount
field of theSpan
in thego.opentelemetry.io/otel
package now only represents the number of attributes dropped for the span itself.It no longer is a conglomerate of itself, events, and link attributes that have been dropped. (Record links/events attribute drops independently #1771)
ExportSpans
in Jaeger Exporter honor context deadline. (Make ExportSpans for Jaeger Exporter honor deadline #1773)go.opentelemetry.io/otel/sdk/export/trace
package is merged into thego.opentelemetry.io/otel/sdk/trace
package. (Merge sdk/export/trace into sdk/trace #1778)TracerProvider
implementation and enable the shutdown of the exporter. (Changes stdout to expose the*sdktrace.TracerProvider
#1800)InstallNewPipeline
andNewExportPipeline
) with theTracerProvider
implementation they create.This enables the caller to shutdown and flush using the related
TracerProvider
methods. (Update Jaeger exporter convenience functions #1822)http://localhost:14250
, for the collector. ( Update Default Value for Jaeger Exporter Endpoint #1824)WithCollectorEndpoint
in the Jaeger exporter to no longer accept an endpoint as an argument.The endpoint can be passed with the
CollectorEndpointOption
using theWithEndpoint
function or by setting theOTEL_EXPORTER_JAEGER_ENDPOINT
environment variable value appropriately. ( Update Default Value for Jaeger Exporter Endpoint #1824)BatchSpanProcessor
for this functionality. (Remove bundler from Jaeger exporter #1830)NewRawExporter
,NewExportPipeline
, andInstallNewPipeline
) no longer accept the removedOption
type as a variadic argument. (Remove bundler from Jaeger exporter #1830)Removed
JAEGER_SERVICE_NAME
,JAEGER_DISABLED
,JAEGER_TAGS
These environment variables will no longer be used to override values of the Jaeger exporter (Update Jaeger environment variables #1752)
Span
ingo.opentelemetry.io/otel/sdk/trace
that is configured to be a new root.This is unspecified behavior that the OpenTelemetry community plans to standardize in the future.
To prevent backwards incompatible changes when it is specified, these links are removed. (Remove links on NewRoot spans #1726)
Because of this
"go.opentelemetry.io/otel/trace".RemoteSpanContextFromContext
is removed as it is no longer needed.Instead,
"go.opentelemetry.io/otel/trace".SpanContextFromContex
can be used to return the current Span.If needed, that Span's
SpanContext.IsRemote()
can then be used to determine if it is remote or not. (Store current Span instead of local and remote SpanContext in context.Context #1731)HasRemoteParent
field of the"go.opentelemetry.io/otel/sdk/trace".SamplingParameters
is removed.This field is redundant to the information returned from the
Remote
method of theSpanContext
held in theParentContext
field. (Update SamplingParameters #1749)trace.FlagsDebug
andtrace.FlagsDeferred
constants have been removed and will be localized to the B3 propagator. (Make TraceFlags spec-compliant #1770)Process
configuration,WithProcessFromEnv
andProcessFromEnv
, and type from the Jaeger exporter package.The information that could be configured in the
Process
struct should be configured in aResource
instead. (Remove process config for Jaeger exporter #1776, Remove the abandoned Process struct in Jaeger exporter #1804)WithDisabled
option from the Jaeger exporter.To disable the exporter unregister it from the
TracerProvider
or use a no-operationTracerProvider
. (Remove the WithDisabled option from Jaeger exporter #1806)CollectorEndpointFromEnv
andWithCollectorEndpointOptionFromEnv
from the Jaeger exporter.These functions for retrieving specific environment variable values are redundant of other internal functions and
are not intended for end user use. ( Update Default Value for Jaeger Exporter Endpoint #1824)
WithSDKOptions
Option
.This option was used to set SDK options for the exporter creation convenience functions.
These functions are provided as a way to easily setup or install the exporter with what are deemed reasonable SDK settings for common use cases.
If the SDK needs to be configured differently, the
NewRawExporter
function and direct setup of the SDK with the desired settings should be used. (Remove the WithSDKOptions from the Jaeger exporter #1825)WithBufferMaxCount
andWithBatchMaxCount
Option
s from the Jaeger exporter are removed.The exporter no longer batches exports, instead relying on the SDK's
BatchSpanProcessor
for this functionality. (Remove bundler from Jaeger exporter #1830)Option
type is removed.The type is no longer used by the exporter to configure anything.
All of the previous configuration these options provided were duplicates of SDK configuration.
They have all been removed in favor of using the SDK configuration and focuses the exporter configuration to be only about the endpoints it will send telemetry to. (Remove bundler from Jaeger exporter #1830)