Skip to content

Collect logs and metrics for InvokeAsync#2349

Closed
FixRM wants to merge 2 commits intoJasperFx:mainfrom
FixRM:main
Closed

Collect logs and metrics for InvokeAsync#2349
FixRM wants to merge 2 commits intoJasperFx:mainfrom
FixRM:main

Conversation

@FixRM
Copy link
Copy Markdown

@FixRM FixRM commented Mar 25, 2026

No description provided.

jeremydmiller added a commit that referenced this pull request Mar 29, 2026
By default, InvokeAsync() uses lightweight tracking without emitting
structured log messages. This adds an opt-in InvokeTracingMode.Full
that emits the same execution started/finished/succeeded/failed log
entries that transport-received messages already produce.

Implemented as a separate TracingExecutor class (rather than runtime
if/then logic in Executor) that is selected at build time based on
the WolverineOptions.InvokeTracing setting. This avoids any overhead
in the default lightweight path.

Closes the community request from PR #2349 with a proper opt-in
approach that doesn't impact default performance.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@jeremydmiller
Copy link
Copy Markdown
Member

I took this as a "requirements doc", but it got in just a tiny bit differently. There's a new flag on WolverineOptions to opt into Full tracing on InvokeAsync. Just watch the release notes for 5.25

@FixRM
Copy link
Copy Markdown
Author

FixRM commented Mar 30, 2026

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants