Richard Simpson

@darkl I actually ran into a perf issue because I was sending not-small json messages over Wamp and the sync logging was waiting to write out massive strings before continueing....

There's no way to it specifically though, since it pulls the logger effectively out of thin error w/ LibLog. So I'd have to set the context of my whole application...

I utilize Serilog, but the issue is I'd like to keep the log level set to Debug and have Json messages not automatically be written, even at Debug level.

Apparently Serilog added a source context minium level override [a few months back](https://nblumhardt.com/2016/07/serilog-2-minimumlevel-override/), so my point is indeed moot. Sorry about that.

Would love this for the exact reason of `deployment` events.

Leaving a comment to avoid closing this issue in 5 days.

@AndrewFreemantle If you don't tackle this, I might here shortly :)

One of the features of doc.crds.dev is to output the underlying CRD yaml for crds from a given repo. e.x.: https://doc.crds.dev/raw/github.com/crossplane/[email protected] I wonder if wouldn't be possible to take those,...

An addition to this may be https://docs.microsoft.com/en-us/dotnet/standard/serialization/system-text-json-source-generation?pivots=dotnet-6-0 either at the jsii level or app level. In theory can make things more explicit as well as improving throughput.

> @kbakk did you ever find a resolution for this? > > On my win10 machine, CDK commands execute painfully slowly (over 60s for a `cdk synth` on the sample-app)....