v1.0.1

Fixed

• Explicitly pass own providers when registering instrumentations (the global providers may be influenced by, for example, Dynatrace OneAgent)

v1.0.0

Added

• Support for tracing native db statements (i.e., cds.run('SELECT * FROM DUMMY'))
• Support for SAP Cloud Logging credentials via user-provided service
• Support for adding @opentelemetry/instrumentation-runtime-node
  • npm add @opentelemetry/instrumentation-runtime-node
  • to cds.requires.telemetry.instrumentations, add:

    "instrumentation-runtime-node": {
      "class": "RuntimeNodeInstrumentation",
      "module": "@opentelemetry/instrumentation-runtime-node"
    }

Changed

• Instrumentations are registered after tracing and metrics are set up
• telemetry-to-dynatrace: Regardless of whether Dynatrace OneAgent is present or not, if dependency @opentelemetry/exporter-trace-otlp-proto is present, @cap-js/telemetry will export the traces via OpenTelemetry.

Fixed

• Tracing of db statements without active span

v0.2.3

Fixed

• Only startup plugin if invoked for runtime (e.g., via cli cds serve)

v0.2.2

Fixed

• Detect build job started via @sap/cds-dk/bin/cds.js

v0.2.1

Fixed

• Avoid credentials validation during cds build

v0.2.0

Added

• Support for local modules (e.g., exporters) via [...].module = '<path relative to cds.root>'
• Disable pool metrics via cds.env.requires.telemetry.metrics._db_pool = false (beta)

Fixed

• Get credentials from cds.env
• Validate existence of credentials only for configured kind
• HTTP attributes only for root spans (reduces trace payload size)

v0.1.0

Added

• Support for own, high resolution timestamps
  • Enable via cds.env.requires.telemetry.tracing.hrtime = true
  • Enabled by default in development profile

v0.0.5

Added

• Register span processor also if tracer provider is initialized by a different module
• Support for so-called Pull Metric Exporter (e.g., @opentelemetry/exporter-prometheus)
• Tenant-dependent DB attributes

Changed

• By default, all system.* metrics collected by @opentelemetry/host-metrics are ignored
  • Disable change via environment variable HOST_METRICS_RETAIN_SYSTEM=true
• Metric exporter's property temporalityPreference always gets defaulted to DELTA
  • Was previously only done for kind telemetry-to-dynatrace
  • Set custom value via cds.env.requires.telemetry.metrics.exporter.config.temporalityPreference

Fixed

• Identification of first-level spans in built-in ConsoleSpanExporter

v0.0.5-alpha.0

Added

• Register span processor also if tracer provider is initialized by a different module

Changed

• By default, all system.* metrics collected by @opentelemetry/host-metrics are ignored
  • Disable change via environment variable HOST_METRICS_RETAIN_SYSTEM=true

v0.0.4

Added

• Re-use TracerProvider and MeterProvider that were initialized by a different module (OpenTelemetry only allows one-time initialization)

Fixed

• NonRecordingSpans are handled correctly