Stefan Jandl

I see. Yeah, we rely on `GetDateTimeOffset()` in `System.Text.Json.JsonElement` and that strictly expects a string to parse. I guess we could check the valuetype when parsing from json to event?

I think we're looking for something like ``` json.TryGetProperty("timestamp", out var timestampElement); DateTimeOffset? timestamp = null; if (timestampElement.ValueKind == JsonValueKind.String) { timestamp = timestampElement.GetDateTimeOffset(); } else if (timestampElement.ValueKind == JsonValueKind.Number)...

Since `Npgsql` has an [integration with Open Telemetry](https://www.nuget.org/packages/Npgsql.OpenTelemetry) this could be something we pick up through there?

It's true that the SDK currently does not provide a proper workflow to support the use-case of multiple DSN or changing the options during runtime. As long as there is...

Given the complexity and that this is not even that popular on other platforms we're lowering the priority and might revisit this in the future.

> A prospective touch-sales customer just mentioned they require .NET Lambda support. The SDK does support Lambda, it just could be improved. Is there anything specific they are missing?

Thanks for raising this. Let me give this a try.

Sorry for the delay but I can reproduce this locally. Interestingly, the SDK does set the traceheader as expected but I suspect the underlying native SDK is overwriting it.

Relies on https://github.com/getsentry/sentry-cocoa/issues/3490

We've got some dev docs regarding span/trace origin (which are used synonymously): https://develop.sentry.dev/sdk/performance/trace-origin