You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* first attempt at otel logs support
* lint files and centralize configs
* add tests
* clean up yarn.lock
* clean up logs
* add back log exporter logic
* clean up docs
* clean up docs and fix otlp protocol
* revert readme docs
* add new otel files
* working version
* fmy
* fmt
* Update packages/dd-trace/src/config_defaults.js
* fix tests
* allow any version of logs api, let opentelemetry api determine the version
* add otlp payload tests
* add telemetry metrics
* some other clean ups
* simplify tests
* use agent hostname to resolve otlp endpoints
* clean up initalization
* parse additional otlp headers
* clean up component args
* clean up docs
* clean up component args
* remove addLogProcessor, init provider with a processor
* support trace-log correlation
* clean up registering provider in tests, and rename exporter arg
* first round of clean ups from PR review
* clean ups part 2
* make things private and clean up tests
* clean up tests
* clean up yarn file
* remove unused configs
* fix context issues
* nother round of clean ups
* group payloads by instrumentation scope
* fix typing
* address review comments
* add better typing, and better support for sending schemaurl
* revert instrumentationScope change to span
* review comments
* clean up protobuf loader file
* lint
* move protos to same dir, this will set up metrics work
* clean up throws
* update protos
* disable log injection when otel logs support is enabled
* update configurations to pass telemetry system tests
* remove useless import
* add more tests
* provide fix for failing system test
* add test case for noop logger and fix mocking for remote config
* add test case for noop logger and fix mocking for remote config
* fix encoding for doubles, remove unused shutdown code, test getLogger params
* remove unused timer and shutdown logic, simplify loggerprovider register and improve tests
* fix comment
* clean up how otel endpoint configs are loaded
* address Ayans comments
* add integration tests
dd-trace-js includes experimental support for OpenTelemetry logs, designed as a drop-in replacement for the OpenTelemetry SDK. This support is primarily intended for logging libraries rather than direct user configuration. Enable it by setting `DD_LOGS_OTEL_ENABLED=true` and use the [OpenTelemetry Logs API](https://open-telemetry.github.io/opentelemetry-js/modules/_opentelemetry_api-logs.html) to emit structured log data:
-`OTEL_EXPORTER_OTLP_LOGS_ENDPOINT` - OTLP endpoint URL for logs (default: `http://localhost:4318`)
412
+
-`OTEL_EXPORTER_OTLP_LOGS_HEADERS` - Optional headers in JSON format for logs (default: `{}`)
413
+
-`OTEL_EXPORTER_OTLP_LOGS_PROTOCOL` - OTLP protocol for logs (default: `http/protobuf`)
414
+
-`OTEL_EXPORTER_OTLP_LOGS_TIMEOUT` - Request timeout in milliseconds for logs (default: `10000`)
415
+
-`OTEL_BSP_SCHEDULE_DELAY` - Batch timeout in milliseconds (default: `5000`)
416
+
-`OTEL_BSP_MAX_EXPORT_BATCH_SIZE` - Maximum logs per batch (default: `512`)
417
+
418
+
Logs are exported via OTLP over HTTP. The protocol can be configured using `OTEL_EXPORTER_OTLP_LOGS_PROTOCOL` or `OTEL_EXPORTER_OTLP_PROTOCOL` environment variables. Supported protocols are `http/protobuf` (default) and `http/json`. For complete OTLP exporter configuration options, see the [OpenTelemetry OTLP Exporter documentation](https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/).
0 commit comments