Use OpenTelemetry (OTel) to generate and route service telemetry, Jaeger to explore traces, and Prometheus to collect and query metrics. The practical architecture is a service instrumented with OTel, optionally a configured OpenTelemetry Collector, then separate trace and metric paths to their respective backends. It is not a one-click setup: SDKs, endpoints, protocols, network access, and backend storage must match your language and deployment.
What each component does
- OpenTelemetry supplies APIs, SDKs, instrumentation libraries, and conventions for creating and exporting telemetry. It is not itself a visualization or storage backend. See the OpenTelemetry overview.
- The OpenTelemetry Collector is an optional, vendor-neutral receiving and processing layer. With the appropriate components and pipeline configured, it can receive, process, enrich, filter, batch, and export telemetry to one or more destinations. It can run near an application as an agent or as a standalone service. See the Collector documentation.
- Jaeger is the trace destination in this architecture: use it to explore distributed traces.
- Prometheus is the metrics destination: use it to collect and query metrics. Its integration paths differ from Jaeger’s trace path.
Think of OTel as the instrumentation and pipeline layer, not as a replacement for either backend. A service can export traces and metrics through different routes even when both signals originate from the same instrumentation.
Trace and metric paths
| Signal | Typical route | Backend role |
|---|---|---|
| Traces | Service instrumentation → OTLP → Jaeger, directly or via a configured Collector | Jaeger stores and presents traces, subject to the deployment’s storage configuration |
| Metrics: OTLP ingestion | Service instrumentation → OTLP metrics endpoint → Prometheus OTLP ingestion | Prometheus ingests and queries metrics |
| Metrics: scrape model | Service or exporter exposes a Prometheus-format endpoint → Prometheus scrapes it | Prometheus discovers or is configured with the scrape target, then collects and queries metrics |
The two Prometheus routes are alternatives, not interchangeable endpoint settings. OTLP ingestion sends metrics to Prometheus; the scrape model exposes a metrics endpoint for Prometheus to poll. Choose based on SDK and backend compatibility, who owns endpoint and target configuration, and the network model in your deployment. The Prometheus OpenTelemetry guide describes its OTLP ingestion path and its configuration.
Build the service-to-backend pipeline
1. Instrument the application and identify it
Use the OpenTelemetry API and SDK or supported language instrumentation to create the signals your service needs. Instrumentation and exporter setup vary by language and runtime; there is no single package or code sample that applies to every service.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- Upgraded Two Zipper Pockets: Forvencer server books feature two secure zipper pockets for better organization of coins, cash, and receipts, ensuring that everything you collect has a safe and secure place
- Smart Storage & Quick Access: Designed with 8 multi-functional compartments, the right side includes a guest receipt pad, while the left has a money pocket, ticket pocket, and credit card slot. Two small clear pockets store bills, receipts, and other visible items. A stitched pen loop ensures you always have your favorite pen ready
- High-quality & Easy to Clean: Crafted from high-quality PU leather with heavy-duty stitching, this server book is built to last. It resists tears, scratches, and its waterproof surface makes cleaning easy with just a damp cloth or a non-chlorine sanitizer
- Perfect Fit for Your Apron: Measuring 5” x 8”, this compact organizer is slightly smaller than other models, making it ideal for bending or sitting while carrying in your server apron. It holds everything a waitress needs—a place for everything
- What's Included: This server organizer comes with multiple open and zippered pockets to store money, receipts, tips, etc. Clear sleeves are perfect for keeping menus or special lists while serving. Available in a variety of colors, allowing you to express yourself even when in uniform
Give telemetry a stable service identity using resource attributes. Prometheus’s guide recommends setting service.name and a unique service.instance.id when instrumentation has not supplied them. The service name identifies the service; the instance ID distinguishes an instance. Apply these consistently so traces and metrics can be interpreted in context.
2. Decide whether to insert a Collector
For a small or direct path, an application can export traces to Jaeger and metrics to the selected Prometheus integration directly. A Collector adds a separate configured hop when you need processing or routing between applications and destinations.
Rank #2
- 5 Pockets & 1 Pen Hook: Keep essentials neatly organized with 5 pockets for cash, cards, receipts, and guest checks, plus a pen holder for easy access.
- Perfect Size for Aprons: Compact 5”x7” size fits comfortably in aprons without poking or bulging. Expandable design ensures easy handling, helping you stay professional and efficient.
- Durable & Easy to Clean: Made from premium, cruelty-free PU leather that’s water-resistant and scratch-proof. Easy to clean, ensuring it stays looking great through busy shifts.
- Stay Organized on the Go: Designed to keep everything securely in place, this server book helps you stay organized even during the busiest shifts, so you can focus on providing great service.
- High Quality at an Affordable Price: A well-crafted server organizer that offers premium quality at a reasonable price, trusted by waitstaff for everyday use.
| Placement | Useful when | Trade-off |
|---|---|---|
| Local agent | You want a Collector near each application or workload to receive telemetry locally | Proximity can fit a service-level network design, but the agent deployment and configuration must be operated across the workloads |
| Standalone Collector | You need a separate receiving and processing tier, such as for centralized routing | Separating the tier gives it an independent scaling and operational boundary, but requires a reachable endpoint and management of that shared service |
Neither placement is universally best. Select based on proximity, processing and routing needs, scaling, and who will operate the Collector. It does not automatically discover every service: configure the relevant receivers, processors, exporters, and service pipelines for the signals and destinations you use.
3. Send traces to Jaeger over OTLP
Jaeger accepts OTLP traces, so an instrumented application can export to Jaeger directly or send OTLP to a Collector that is configured to export them. The JavaScript exporter documentation includes a local example with a Jaeger UI on port 16686 and OTLP listeners on 4317 and 4318. Those are ports in that documentation’s example, not guaranteed ports for every package or deployment. Consult the JavaScript exporter documentation and the configuration for the exact Jaeger release you run.
Rank #3
- Built for Heavy-Duty Shifts — Unlike Vinyl, PU Leather Won't Crack: This server books for waitress for Reinforced odorless PU leather with double-stitched seams resists tears and scratches far better than vinyl, which cracks and peels over time. The textured surface adds grip and an anti-slip effect on counters and tabletops for steadier writing. The thickened rigid writing surface stays perfectly flat for comfortable order-taking in high-traffic dining rooms and busy bars. This waitress book design works for both left- and right-handed users — built to withstand fast-paced service without warping.
- Wipes Clean in Seconds — Water-Resistant Surface, Hand Wipe Only: This black server book spill-resistant surface wipes clean with a damp cloth between tables — coffee spills and food grease come right off. Avoid alcohol-based sanitizers; for stubborn oil stains, wipe with mild soapy water, let sit 2 minutes, then wipe. This waitress book is not machine washable — hand wipe only to preserve the PU leather finish. Maintains a sharp, professional look shift after shift.
- 7 Compartments Keep Cash, Cards & Tips Organized: This serving book Secure zipper pocket (1,000+ open/close cycles) is designed for coins and small bills (For maximum security, keep coin pocket moderately filled) — use the main compartment for unfolded bills up to 6.75 inches. Clear receipt windows are made from thickened, scratch-resistant PVC for lasting clarity and durability. The waitress books for servers Clear card slots that hold multiple cards and an elastic pen loop keep everything visible and accessible. Fits standard 3.5" x 6.75" guest checks without folding, so cash, cards, and order slips stay organized during rush hours.
- Slim Apron Fit — Elastic Pen Loop Fits Standard & Jumbo Pens: This server book Compact 5" x 8" slim profile slips into any apron pocket and sits flush against your waist for unrestricted movement — whether bending, sitting, or rushing through a busy dining room. The elastic pen loop stretches to fit both standard pens and jumbo markers, so you always have your preferred writing tool ready. The waitress book Holds all shift essentials without adding weight or bulk.（Pen is not included and must be purchased separately）
- Professional Server Gear for Waitstaff, Bartenders & Cashiers: Streamline orders, tips, and payments with a server book built for waitstaff, bartenders, cashiers, and fast-food crews — not just waitresses. This server books for waitress is Ideal for fine dining, busy cafes, high-volume bars, and fast-food counters. A practical gift for new staff or a reliable upgrade for seasoned teams who demand professional appearance and secure cash handling. This waitress book built for daily professional use with durable construction that holds up shift after shift.
For any language, verify that the exporter protocol and destination endpoint agree with the Jaeger receiver that is enabled and reachable in your deployment. If you use a Collector, verify its receiving protocol as well as its configured trace-export pipeline.
4. Choose one Prometheus metrics route
OTLP ingestion: configure the SDK or exporter to send OTLP metrics to Prometheus’s OTLP endpoint, or route the metrics through a Collector configured for that destination. The Prometheus guide notes that the endpoint appends /v1/metrics to the base URL specified in OTEL_EXPORTER_OTLP_METRICS_ENDPOINT. Account for that behavior when setting the base URL; do not assume the variable should contain the full final path.
The same guide describes a default metric push interval of 60 seconds and demonstrates changing it to 15 seconds. Those are configuration details in the guide, not universal recommendations. Choose an interval that fits your telemetry needs and the capacity and configuration of your deployment.
Prometheus-format scraping: expose a Prometheus-format metrics endpoint using an exporter or supported instrumentation, then configure Prometheus to scrape that endpoint. In this model, Prometheus must be able to reach the endpoint and have it configured as a scrape target. This is distinct from sending OTLP metrics to Prometheus; enabling one path does not by itself configure the other.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- Compact Size: Measuring 4.7 x 7.6 inches, this server book is slim, lightweight, and fits effortlessly into your apron pocket. It's designed to hold a standard guest check book (not included), making it an ideal tool for busy waitstaff.
- Ample Storage and Functionality: Featuring 7 pockets and compartments, this server book provides plenty of space to keep all your essentials organized. The tiny front pocket is perfect for holding guest credit cards, while see-through pockets on both sides offer quick access to reference lists. Plus, it even holds a pen when closed without adding bulk.
- Premium Material with a Stylish Touch: Crafted from high-quality PU faux leather with classic solid black, this server book feels luxurious in your hand. It’s waterproof exterior and interior are resistant to water, scratches, punctures, and heat, ensuring durability and easy cleaning.
- Professional Appearance: The smooth, rich black finish and meticulously crafted seams and stitching give this server book a polished, professional look, making it a reliable companion for any server.
- Durable and Easy to Clean: Designed to withstand the demands of the job, this server book is built to last. The waterproof material not only protects against spills and stains but also wipes clean easily, maintaining its pristine appearance even with regular use.
Verify the end-to-end setup
Test each signal path independently before diagnosing dashboards or queries. Check the application’s telemetry output, the receiving endpoint, and the destination configuration.
- Identity: confirm the emitted resource has the intended
service.nameand, where needed, a uniqueservice.instance.id. - Endpoint and protocol: confirm the exporter points to a reachable receiver and that both sides use a compatible protocol. For Prometheus OTLP metrics, account for the documented
/v1/metricssuffix behavior. - Collector pipeline: if present, confirm the Collector has receivers for incoming data, processors you intend to use, exporters for the destination, and a service pipeline connecting them. A running Collector alone does not establish that telemetry is routed.
- Trace arrival: generate a request that should produce a trace, then check Jaeger for it. If absent, trace the route from SDK export through any Collector to the Jaeger OTLP receiver.
- Metric arrival: for OTLP, check Prometheus’s configured ingestion path; for scraping, check that Prometheus can reach the exposed endpoint and is configured to scrape it. Troubleshoot the path you actually selected.
Plan backend operations and security separately
The data-flow examples do not determine production storage or operations. Choose and configure Jaeger trace storage and Prometheus metric retention and query behavior for your deployment; the integration paths alone do not specify those policies. Likewise, a local example does not provide a complete production design for authentication, TLS, access control, or retention. Decide how applications, Collectors, and backends communicate securely, and restrict access to telemetry and query interfaces according to your environment.
Finally, pin the configuration to the versions and distributions you deploy. SDK package names, supported Collector components, Jaeger listeners, Prometheus settings, and command-line flags can change. Verify each endpoint and option against the documentation for the exact language SDK, Collector distribution, Jaeger release, and Prometheus release in use.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
