Opentracing Intermediate Training
Keep OpenTracing code working on OpenTelemetry through shims, route traces through the Collector, and use traces to find latency and error root causes. Learn Opentracing through a clear Foundation to Advanced path, with hands-on labs, live cohort options, certification support and full LMS access.
Last updated
Self-paced video subscription
Billed yearly at ₹9,996. This includes all four levels, complete LMS access for one year, plus 20+ additional courses and 50+ tools access.
- All four Opentracing levels in one price.
- 20+ additional courses and 50+ tools included, even when subscribing to one course.
- Best fit for learners who want full-library access and flexible progress.
Live & Interactive session
Instructor-led cohort, max 8 to 10 hours, with demos, labs, Q&A, assignments and practical review.
- Live small-batch cohort from soon.
- Interactive discussion and lab troubleshooting.
- Recommended for teams that need guided implementation.
1:1 Live training
The same agenda, taught one-to-one by the trainer. Start immediately, without waiting for the next batch. Max 8 to 10 hours, one-to-one.
About Opentracing Intermediate Training.
Understand where Opentracing fits in modern software delivery, what this level covers, and how the program builds practical confidence step by step.
Program overview
Opentracing is taught as a practical technical skill for modern engineering, operations and platform teams. The course explains where the tool fits, how it is used in real delivery environments, and how learners can apply it through guided practice.
This DevOpsSchool Opentracing program is built for working professionals who want usable skills instead of only conceptual exposure. The training emphasizes live examples, workflow clarity, operational controls and progressive skill depth from Foundation to Intermediate.
Private Opentracing training for delivery teams, platform groups and engineering organizations.
DevOpsSchool provides corporate Opentracing training for teams that need faster adoption, workflow standardization, administrative control, integration guidance and governance-ready rollout. Private batches can be aligned to development practice, release workflow, access model, maturity level and internal tooling.
- Private online or classroom delivery for engineering teams
- Aligned to Opentracing usage maturity, admin depth and collaboration patterns
- Useful for rollout, migration, governance and workflow consistency goals
- Can be tailored for developers, administrators, DevOps teams and leadership stakeholders
Why teams use DevOpsSchool
DevOpsSchool combines live demonstration, practical workflow discussion, implementation-oriented examples, and strong post-session learning support. That makes the training more usable for real teams than generic slide-led courses.
Choose any level. The page still shows the full progression.
Foundation, Essential, Intermediate and Advanced are presented as one linked training flow. Self-paced buyers get all levels by default, even if they start from only one course page.
Instructor-led, self-paced and corporate delivery options.
Compare delivery format, duration, level access and batch style. Fees are shown only in the top decision panel and once again after the agenda.
| Duration | Mode | Level access | Batch |
|---|---|---|---|
| 8 to 10 Hrs. max | Live & Interactive | Intermediate | Public batch |
| 8 to 10 Hrs. max | 1:1 Live training | Intermediate | Starts immediately |
| 1 year LMS access | Self-paced video | All 4 levels | Anytime access |
| 3 Days | Corporate | Opentracing Intermediate Training | Private team batch |
What learners should be able to do after Opentracing training.
The outcomes are written for practical delivery teams: developers, DevOps engineers, release engineers, administrators and technical leads.
Understand distributed tracing
Explain spans, context propagation and the OpenTracing data model in real systems.
Instrument services correctly
Add consistent, tested tracing to services in several languages and protocols.
Modernise tracing at scale
Bridge and migrate to OpenTelemetry and operate governed trace pipelines with smart sampling.
Why this skill, what you will achieve, and who should attend.
Use this section to decide whether the course matches your role, current experience and expected Opentracing responsibilities before reviewing the detailed agenda.
Why Opentracing matters
- Opentracing helps teams standardize a critical part of their software delivery, infrastructure, automation or operations workflow.
- It gives learners a repeatable way to move from basic usage to confident execution in team and enterprise environments.
- For DevOps and platform teams, Opentracing becomes more valuable when connected with automation, governance, monitoring and delivery practices.
- Teams using Opentracing effectively reduce ad-hoc execution and move toward consistent engineering standards.
Objectives
- Understand Opentracing concepts, architecture, terminology and operational usage patterns.
- Learn practical configuration, workflow design, access controls, team usage and quality practices.
- Apply Opentracing in real delivery workflows using automation, integrations, traceability and governance patterns.
- Build practical confidence to use Opentracing for individual, team and organizational use cases.
Pre-requisites
- Basic computer literacy and familiarity with software development workflows.
- Helpful but not mandatory: introductory DevOps, cloud, automation or software delivery awareness.
- No deep programming background is required for the Foundation and Essential levels.
Who this course is for
- Developers, administrators and engineers who need practical Opentracing usage skills.
- DevOps engineers, release engineers, SREs and platform teams managing delivery standards.
- Engineering leads and technical managers responsible for workflow quality, access controls and governance.
- Corporate teams migrating to or standardizing on Opentracing.
Small-batch live training starts every month.
Weekday batches start on the 1st and weekend batches on the first Saturday of every month. One-to-one (1:1) training can start immediately; corporate sessions are scheduled on demand.
Weekend live batch
Starts on the first Saturday of every month. Weekend sessions with demos, labs and Q&A; max 10 learners.
Weekday live batch
Starts on the 1st of every month. Weekday sessions for working professionals and distributed teams; max 10 learners.
Ask advisorAgenda depth up to the selected level.
This page shows the learning flow from Foundation through Intermediate. Each level adds to the previous one, and the agenda stops at the current page level. Day counts are for corporate (day-wise) delivery; live online batches cover the same agenda in max 8 to 10 hours.
Foundation Level: tracing concepts, OpenTracing data model and JaegerDay 1
- Why distributed tracing: requests crossing many services, latency attribution and limits of logs and metrics alone
- OpenTracing project history: CNCF origins, the vendor-neutral API idea, the 2019 merger into OpenTelemetry and archival
- Data model: traces, spans, operation names, start and finish timestamps and span duration
- Span relationships: SpanContext, ChildOf and FollowsFrom references
- Tags, logs and baggage: span tags for indexing, timestamped span logs and request-scoped baggage items
- Tracer interface: StartSpan options, GlobalTracer registration and the no-op tracer
- Context propagation: Inject and Extract with text map, HTTP headers and binary carriers
- Jaeger architecture: client, agent, collector, query service and storage, and Jaeger v2 on the OpenTelemetry Collector
- Jaeger all-in-one: running it in Docker, opening the UI and searching traces by service and tags
- First trace: instrumenting a hello world service in Go or Python with an OpenTracing-compatible tracer
- Two-service trace: propagating context over HTTP and viewing the parent and child spans in Jaeger
Essential Level = Foundation + instrumenting real services in several languagesDay 2 · 2 days cumulative
- Java instrumentation: ScopeManager, activating spans, try-with-resources scopes and opentracing-contrib modules
- Go instrumentation: context.Context propagation, StartSpanFromContext and middleware for net/http
- Python and Node.js instrumentation: contextvars-based scope managers and Express or Flask middleware
- gRPC tracing: client and server interceptors and metadata propagation
- Database and cache spans: JDBC, SQL and Redis calls with db.type, db.statement and peer tags
- Messaging spans: Kafka or RabbitMQ producers and consumers with FollowsFrom references
- Standard tag conventions: span.kind, http.method, http.url, http.status_code, component and error
- Error handling in spans: setting the error tag, logging exceptions with event, message and stack fields
- Zipkin as a backend: B3 propagation headers, Zipkin server and comparing its UI with Jaeger
- Sampling configuration: constant, probabilistic and rate-limiting strategies and remote sampling in Jaeger
- Testing instrumentation: MockTracer assertions on finished spans, tags and references
- Instrumentation guidelines: span naming, granularity and what to trace first in a service
Intermediate Level = Essential + OpenTelemetry bridge, pipelines and trace analysisDay 3 · 3 days cumulative
- OpenTracing to OpenTelemetry mapping: Tracer, Span, SpanContext, references, tags and logs to OTel concepts
- OpenTracing shim: running legacy instrumentation on the OpenTelemetry SDK in Java, Go and Python
- W3C Trace Context: traceparent and tracestate headers and coexisting with B3 and uber-trace-id
- OpenTelemetry Collector: receivers for Jaeger, Zipkin and OTLP, batch processor and exporters to several backends
- Auto-instrumentation alongside manual spans: Java agent and zero-code options with existing OpenTracing code
- Service mesh tracing: Envoy and Istio generated spans and header forwarding requirements in applications
- Trace analysis: critical path, latency outliers, comparing traces and service dependency graphs
- Root cause analysis: from a slow endpoint to the misbehaving downstream call using tags and span logs
- Grafana Tempo and TraceQL: storing traces cheaply and querying spans by attributes and duration
- Span metrics: deriving request rate, error and duration metrics and service graphs from traces
- Data hygiene: keeping secrets and personal data out of tags and baggage, attribute redaction in the Collector
- Troubleshooting broken traces: lost context in thread pools and async code, clock skew and dropped spans
Choose live training or a full year of self-paced access.
If someone buys Foundation, Essential, Intermediate or Advanced as self-paced video, the price stays the same and access is granted to all four levels by default.
Self-paced video subscription
Billed yearly at ₹9,996. This includes all four levels, complete LMS access for one year, plus 20+ additional courses and 50+ tools access.
- All four Opentracing levels in one price.
- 20+ additional courses and 50+ tools included, even when subscribing to one course.
- Best fit for learners who want full-library access and flexible progress.
Live & Interactive session
Instructor-led cohort, max 8 to 10 hours, with demos, labs, Q&A, assignments and practical review.
- Live small-batch cohort from soon.
- Interactive discussion and lab troubleshooting.
- Recommended for teams that need guided implementation.
1:1 Live training
The same agenda, taught one-to-one by the trainer. Start immediately, without waiting for the next batch. Max 8 to 10 hours, one-to-one.
- Start immediately: no waiting for the monthly batch.
- One learner, one trainer: full attention on your questions.
- Sessions planned around your working hours.
- Your pace, with examples from your own projects and tools.
Method of training and assessment.
The course emphasizes practical demonstration, hands-on labs and assignment-based validation instead of passive lecture-only learning.
| SL | Method of training and assessment | Weightage |
|---|---|---|
| 1 | Understanding the problem space | 5% |
| 2 | Concept discussion | 10% |
| 3 | Live demo and walkthrough | 25% |
| 4 | Lab and hands-on exercises | 50% |
| 5 | Assignments and evaluation | 10% |
Labs, exercises and real workflow practice.
Every level moves from explanation to hands-on practice, review and troubleshooting.
Trace a request across two services
Run Jaeger all-in-one, instrument a frontend and a backend service with OpenTracing, propagate context over HTTP and inspect the resulting trace timeline.
Instrument a polyglot order system
Instrument a Java API, a Go worker and a Python service connected by gRPC and Kafka, add database spans and verify the instrumentation with MockTracer tests.
Bridge legacy tracing to OpenTelemetry
Run the existing OpenTracing services through the OTel shim and Collector into Jaeger and Tempo, switch to W3C propagation and trace a slow request to its root cause.
Opentracing is taught as part of a working delivery ecosystem.
You learn where the tool sits in the wider engineering workflow, not in isolation.
Core foundations
Terminology, concepts, architecture and the operating model behind the tool.
Workflow traceability
Map practical work to tasks, approvals, documentation and delivery visibility.
Automation and integration
Use Opentracing with validation checks, automation hooks and delivery workflows.
Governance controls
Operate with permissions, approvals, policy checks and production-safe workflows.
How your practical work is assessed.
Your certificate is backed by labs, assignments, capstone thinking and completion evidence.
Assignments
Level-specific assignments verify setup, configuration, workflow quality and operating discipline.
Hands-on validation
Learners are expected to complete practical usage, automation and troubleshooting exercises.
Completion record
Certificate issuance is tied to demonstrated participation, practical completion and course-level coverage.
Led by Rajesh Kumar and the DevOpsSchool practitioner network.
Training is grounded in practical DevOps, SRE, security, release and platform engineering experience with real enterprise delivery context.
Earn a DevOpsSchool Opentracing certificate.
Completion includes a digital certificate with credential details, practical assignments and a learning record aligned to the selected Opentracing level.
Certificate verificationCertificate of Completion
Opentracing Intermediate Training
Unique credential ID, verifiable online
What learners say about training with Rajesh Kumar.
“Rajesh is very good trainer. Rajesh was able to resolve our queries and question effectively. We really liked the hands-on examples covered during this training program.”
“Very well organized training, helped a lot to understand the AWS concept and detailed related to various tools. Very helpful”
“The training was very useful and interactive. Rajesh helped develop the confidence of all.”
Rated 4.6 on Google · All testimonials · Video reviews on YouTube
Quoted as published, from learners in Rajesh Kumar's live trainings across DevOpsSchool courses.
Used by developers, DevOps engineers, release leads and engineering managers.
Private batches are available for teams that want the same agenda aligned to their own tools and workflows.
Why this Opentracing path is different.
The value is not only one course. The subscription unlocks the full learning ecosystem for one year.
| Feature | DevOpsSchool Opentracing Training | Typical short course |
|---|---|---|
| Levels | Foundation, Essential, Intermediate, Advanced | Single generic syllabus |
| Self-paced access | All four levels plus 20+ courses and 50+ tools | Usually one course only |
| Live training | Demos, labs, Q&A and assignment review | Often lecture-heavy |
| Certificate | DevOpsSchool completion certificate | Varies by provider |
Questions learners ask before joining.
Does Foundation cost less than Advanced?
No. Self-paced pricing is intentionally the same because access includes all four levels by default.
What is included in the yearly subscription?
One year of complete LMS access, all four levels for the selected course, plus 20+ additional courses and 50+ tools access.
Can corporate teams request customization?
Yes. The live format can be aligned to team tools, governance requirements, workflows and internal delivery standards.
What is the recommended sequence?
Foundation → Essential → Intermediate → Advanced. The agenda is designed so each level builds on the previous one.
Talk to DevOpsSchool before choosing the batch.
Use this support section for batch questions, corporate planning, LMS access clarifications, or guidance on which Opentracing level fits your team.
India / Worldwide: +91 99057 40781
USA: +1 (469) 756-6329
Email: contact@DevOpsSchool.com
Chat on WhatsAppExtend the course with articles, explainers and workflow guidance.
Continue learning with supporting articles that connect Opentracing practices to DevOps, automation, governance and delivery workflows.
Training snapshots and certificate preview.
A look at the completion certificate and the course.
Certificate preview
See what course completion evidence looks like.
Tool-focused training
Course visuals reinforce the Opentracing workflow and subject area.
Live batch experience
Training supports live online, private team and workshop-style delivery.
Start Opentracing Intermediate training.
Next weekday batch starts on the 1st; weekend batch on the first Saturday. Batches are capped at 10 learners. Send your details and DevOpsSchool will share the syllabus and batch options.