Step 19 of 21
·
5 minutes
Debug Like a Detective
The Scenario
After a routine redeploy, credit card creation jobs are taking 10x longer
than usual. Users are complaining, but the code hasn't changed.
We need to identify which step or resource is causing the slowdown.
The Challenge
How do we identify which step or resource is slowing down our jobs?
The Solution
JobRunr Pro integrates with
OpenTelemetry to provide detailed job traces:
# In application.properties
management.tracing.sampling.probability=1.0
management.opentelemetry.tracing.export.otlp.endpoint=http://localhost:4318/v1/traces
jobrunr.jobs.metrics.otel-observability.enabled=true
JobRunr automatically creates spans for job execution, so you can pinpoint
exactly where time is being spent — whether it's the database, an external API,
or your own code.
Read the documentation →
Try It Yourself
- Register a credit card and watch the job complete
- Open Jaeger and search for service "storyline-demo"
- Analyze the different spans of the job's trace to find the bottleneck
You need to log in to perform write operations. You can still view the code solution and dashboard.
Jaeger is not available in this live demo. Run the demo locally to explore distributed traces.
This step focuses on dashboard exploration. No specific code to display.