Custom Spans and nesting

[tsteckenborn]

Hello everyone,

What's the current strategy and behaviour around doing your own spans within your coding?

trace
.getActiveSpan()!
.spanContext(),

Doesn't seem to work anymore with the latest updates, yet you can get e.g. the context via:

context
.active()
// @ts-expect-error
.getValue(cds?.context?._otelKey)
.spanContext(),

In case we use this data to create custom spans having the cap span as a parent, are further spans by the plugin taking the currently active span, or the span set by the plugin?

[tsteckenborn]

Hi @sjvans, might be interesting to also enable users to easily create
a) custom spans
b) span events (or e.g. also add cap logs to the span events)
so that everything can easily be seen or more fine granularily watched via otel traces

[soccermax]

Hi @tsteckenborn,

yes some guidance would be nice. I managed to include telemetry into my NPM package with the following coding:
https://github.com/cap-js-community/event-queue/blob/23728cb3a1020f2ac512a102b6670a77ab473ae1/src/shared/openTelemetry.js#L15

This is nesting traces: always you call the trace function it's creates a span below the parent span. At the end it looks like this: