You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It would be useful when using a WireMock in .NET Aspire for the OTEL data to be populated as expected in the OTEL dashboard. This facilitates troubleshooting and the development process.
Describe the solution you'd like
I would expect to see appropriate headers like traceparent respected and traces, logs, metrics to be pushed to the OTEL collector behind the dashboard.
I think it would be a matter of installing the extension in the WireMock container and pointing it at the OTEL connection. The Aspire IResourceWithEnvironment interface provides access to all the OTEL_* env vars that can be utilized to send the telemetry to. You can see an example ContainerResourcehere from my KrakenD component. I then just use those env vars to tell my gateway where to send the logs, metrics and traces to (i.e.: the OTEL collector the Aspire Dashboard runs). Does that help @StefH ?
A gap for me is how to install the extension. I haven't worked with the Java wiremock solution directly.
Is your feature request related to a problem? Please describe.
It would be useful when using a WireMock in .NET Aspire for the OTEL data to be populated as expected in the OTEL dashboard. This facilitates troubleshooting and the development process.
Describe the solution you'd like
I would expect to see appropriate headers like
traceparent
respected and traces, logs, metrics to be pushed to the OTEL collector behind the dashboard.Describe alternatives you've considered
N/A
Is your feature request supported by WireMock (java version)? Please provide details.
Based on a quick search it appears an extension might be under development: https://github.com/wiremock/wiremock-otel-extension
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: