This sample shows how to configure OpenTelemetry to capture workflow traces and SDK metrics using the .NET metrics API.
The main advantage over forwarding metrics directly from the Core SDK is greater customizability; as an example, tags can be re-named as needed, or the metrics can be processed/exported consistently with other .NET code.
This sample also shows how to configure custom metrics from both an activity and a workflow in a replay-safe manner.
To run, first see README.md for prerequisites.
Then, run the following from one directory up to start the .NET Aspire Dashboard which will collect telemetry. The dashboard UI is available at http://localhost:18888.
docker compose up
Then, run the following from this directory in a separate terminal to start the worker:
dotnet run worker
Then in another terminal, run the workflow from this directory:
dotnet run workflow
The workflow will complete.
Traces can be viewed at http://localhost:18888/traces.
You can select either worker or workflow for traces; both should show the same trace. The workflow should appear and when clicked, may look something like:
Metrics can be viewed by clicking the metrics tab on the dashboard.
Similar to traces, you can select either worker or workflow.
worker will show the metrics emitted by the worker. It may look something like:
workflow will show the metrics emitted by the client. It may look something like:
