feat(tracing): Implement Jaeger/OpenTracing provider with configuration options
- Added Punycode encoding implementation for cookie handling. - Introduced serialization for cookie jar with JSON support. - Created a comprehensive README for the tracing provider, detailing configuration and usage. - Developed a configuration structure for tracing, including sampler and reporter settings. - Implemented the provider logic to initialize Jaeger tracer with logging capabilities. - Ensured graceful shutdown of the tracer on application exit.
This commit is contained in:
@@ -0,0 +1,18 @@
|
||||
# Copyright The OpenTelemetry Authors
|
||||
# SPDX-License-Identifier: Apache-2.0
|
||||
|
||||
# extra settings to be merged into OpenTelemetry Collector configuration
|
||||
# do not delete this file
|
||||
|
||||
## Example configuration for sending data to your own OTLP HTTP backend
|
||||
## Note: the spanmetrics exporter must be included in the exporters array
|
||||
## if overriding the traces pipeline.
|
||||
##
|
||||
# exporters:
|
||||
# otlphttp/example:
|
||||
# endpoint: <your-endpoint-url>
|
||||
#
|
||||
# service:
|
||||
# pipelines:
|
||||
# traces:
|
||||
# exporters: [spanmetrics, otlphttp/example]
|
||||
Reference in New Issue
Block a user