Recommended Free Tools
Cloudflare Traces shows the request path through Cloudflare’s edge, Workers, and the handoff to your origin. It is not, by itself, a complete trace of every downstream service. Datadog and Honeycomb are backends for application-wide distributed tracing. To see one end-to-end trace, Cloudflare and your origin services must preserve W3C trace context, emit compatible spans, and export those spans to the same OpenTelemetry destination.
What each product is responsible for
The three products occupy different layers of an observability system. Cloudflare Traces is a request-path view inside Cloudflare. Datadog and Honeycomb store, index, and help you investigate spans emitted by your applications and infrastructure.
As an Amazon Associate I earn from qualifying purchases.
| Question | Cloudflare Traces | Datadog distributed tracing | Honeycomb tracing |
|---|---|---|---|
| Primary boundary | Cloudflare edge, supported rules, cache and routing decisions, Workers, and origin handling | Application and infrastructure telemetry collected in Datadog’s APM and observability platform | Application telemetry queried across Honeycomb environments and service datasets |
| Who creates most spans? | Cloudflare-managed components; Worker spans require Workers tracing | Your services, using Datadog’s SDK/distribution, OpenTelemetry with Datadog components, an upstream Collector, or direct OTLP | Your services, normally instrumented with OpenTelemetry and exported over OTLP |
| Can it show downstream microservices automatically? | No. The origin and downstream services must be instrumented and must preserve context | Yes, when those services emit compatible spans and the trace is ingested correctly | Yes, when those services emit spans into the same environment with a shared trace ID |
| Investigation model | A selected request displayed as a hierarchy of Cloudflare spans | Integrated APM, service and infrastructure workflows, depending on the selected ingestion path | High-dimensional queries across events and service datasets |
Use Cloudflare Traces to answer questions such as “Which edge rule, cache decision, Worker, or origin handoff affected this request?” Use Datadog or Honeycomb to answer “What happened after the request left the edge, and which service caused the latency or error?”
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhat Cloudflare Traces contains
A production request hierarchy
Cloudflare’s Traces interface opens a selected production request as a hierarchy of spans. Depending on the request and enabled features, that hierarchy can include supported security rules, transformations, cache decisions, routing, Workers, and origin handling. This is a view of processing performed by Cloudflare and of the request’s edge-to-origin path, not a promise that every application function is represented.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Workers are conditional
Worker activity appears only when Workers tracing is enabled. Workers tracing follows OpenTelemetry (OTel) standards, so Worker spans can participate in an OpenTelemetry-based pipeline rather than being confined to Cloudflare’s interface.
Selection and sampling affect what exists
Cloudflare records a full request path after a request is selected for tracing. Workers tracing also supports a configurable head-sampling rate. Cloudflare documentation uses head_sampling_rate: 0.05 as an example, which represents 5 percent of eligible traces. It is an example configuration, not a universal recommendation or a measured performance target. Check the current Cloudflare plan limits and sampling behavior before choosing a production value.
What it does not do
Cloudflare does not automatically instrument your origin, database, queue, or internal microservices. Seeing an origin-handling span in Cloudflare does not mean you have spans for the code that ran behind that origin. The boundary is important: Cloudflare can show that it forwarded a request and how long that handoff took, while only your application instrumentation can show what happened afterward.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How one trace crosses Cloudflare and your services
W3C Trace Context is the joining mechanism
Cloudflare uses W3C Trace Context. A trace context contains identifiers that let independently produced spans refer to the same distributed trace. Cloudflare rejects incoming trace context by default. If you want an incoming context to be used, configure the appropriate trust behavior; if you want Cloudflare to pass context onward, enable Forward to origin.
Forwarding is not instrumentation
Forwarding context only sends the trace headers with the request. Cloudflare’s configuration documentation explicitly notes that forwarding context does not instrument the origin or create origin spans by itself. Your origin must use an OpenTelemetry SDK, a compatible vendor SDK, or another instrumentation path that reads the W3C headers and creates child spans.
The same destination is required for a single visible trace
To render one combined trace in an external backend, export Cloudflare spans and origin spans to the same OpenTelemetry destination. If Cloudflare sends spans to one backend while the origin sends spans to another, each system can have valid data but neither can display a single complete trace. Matching trace IDs alone is not enough when the data is stored in separate systems.
Propagation must survive every hop
After the origin receives the request, every downstream service must preserve the W3C context when calling another service. A service that drops or replaces the headers creates a new trace segment. The result can look like a missing service, a disconnected trace, or several unrelated traces with similar timestamps.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Datadog as the distributed-tracing backend
Four supported setup families
Datadog documents four relevant ways to collect distributed traces:
- Datadog SDK with Datadog’s distribution. This is the most vendor-specific route and can expose Datadog features through its own instrumentation and agent model.
- OpenTelemetry SDK with Datadog’s distribution. You instrument with OpenTelemetry while using Datadog-provided components for collection or export.
- OpenTelemetry SDK with an upstream OpenTelemetry Collector. The Collector becomes the processing and routing layer between services and Datadog.
- Direct OTLP ingest. Services or an intermediary send OTLP data directly to Datadog’s intake.
Datadog’s compatibility matrix distinguishes which distributed-tracing and related features are available with each setup. Choose the path based on the correlations, trace metrics, automatic instrumentation, and other Datadog features you require, rather than assuming that every OTLP route has identical capabilities.
Where Cloudflare fits
Cloudflare can export Workers and edge trace data through an OTLP destination. The exact Datadog endpoint format, site selection, and authentication requirements are operational details that change by account and region; take them from the current Cloudflare and Datadog documentation when configuring the destination. The architectural requirement does not change: the Datadog intake receiving Cloudflare spans must be the same logical destination that receives the origin and service spans for the trace.
When Datadog is the practical choice
Datadog is a fit when your team wants distributed traces alongside a broad observability suite and is prepared to standardize on Datadog’s agent or distribution, or to validate which features remain available with direct OTLP. It can reduce the number of separate investigation tools for teams already operating their metrics, logs, and infrastructure views there. The trade-off is that setup choices can affect feature coverage, so test the selected ingestion family with a representative trace before rolling it out widely.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchHoneycomb as the distributed-tracing backend
OTLP-first ingestion
Honeycomb accepts OpenTelemetry Protocol data over gRPC, HTTP/protobuf, and HTTP/JSON. Its documentation recommends OpenTelemetry for first-time instrumentation. Existing OpenTracing, Zipkin, or Jaeger data can be converted through the OpenTelemetry Collector, allowing a gradual migration rather than requiring every service to change at once.
Environment placement is part of trace design
Honeycomb’s trace model requires all spans in a distributed trace to be in the same environment for the trace to render correctly in the user interface. Service datasets represent spans from individual services, and the query engine finds spans across those datasets when they share a trace ID. Therefore, environment selection is not merely an administrative choice: placing edge spans in one environment and origin spans in another can prevent a trace from appearing as one connected object.
Resource attributes must be consistent
Use consistent resource attributes, especially service.name, across Cloudflare-exported data and your application telemetry. Keep the trace-ID fields intact as data passes through collectors and exporters. Inconsistent service naming does not necessarily break propagation, but it makes service maps, filtering, and cross-service investigation harder to interpret.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
When Honeycomb is the practical choice
Honeycomb suits teams that prioritize high-dimensional trace investigation and provider-neutral OpenTelemetry ingestion. Its model is especially useful when engineers need to query unusual combinations of attributes across services rather than follow only prebuilt service dashboards. The operational constraint is strict environment consistency for every span in a trace.
Step-by-step implementation pattern
1. Define the trace boundary
List the components a user request can traverse: Cloudflare security and routing, a Worker, the origin gateway, application services, databases, queues, and any asynchronous workers. Decide which of these need spans for your incident and performance questions. Cloudflare Traces covers the edge portion; your instrumentation plan covers the rest.
2. Enable the Cloudflare tracing features you need
- Enable Cloudflare Traces for the production requests you intend to inspect.
- If a Worker must appear in the hierarchy, enable Workers tracing.
- Choose a head-sampling rate that fits traffic volume, diagnostic needs, and current plan limits. Treat the documented 0.05 example as a starting illustration, not a required value.
- Decide whether Cloudflare should retain traces in its own interface, export them externally, or do both. Retention and quota behavior should be checked against the current plan documentation.
3. Configure the external OTLP destination
Select Datadog or Honeycomb, then configure Cloudflare’s OTLP destination with the endpoint, authentication, and site or environment settings required by that provider. Do not reuse credentials or endpoint assumptions between providers. Confirm that the destination accepts the protocol and signal format Cloudflare emits.
4. Forward W3C context to the origin
In Cloudflare’s tracing configuration, enable Forward to origin when the origin is prepared to trust and process the headers. Review your trust boundary before accepting incoming context from untrusted clients; propagation settings should match your security policy.
5. Instrument the origin and downstream services
Install an OpenTelemetry SDK, a selected vendor SDK, or an approved framework integration in the origin. Configure it to extract W3C Trace Context from incoming requests, create server and internal spans, and inject context into outbound calls. Repeat the propagation setup for each service, queue producer, and queue consumer that should be connected.
6. Export all spans to the same backend
Configure Cloudflare and the origin-side SDK or Collector to export to the same Datadog intake or the same Honeycomb environment. If you use an OpenTelemetry Collector, ensure its exporters route both Cloudflare-originated and application spans to that destination rather than splitting them across pipelines.
7. Verify identity and naming
- Check that the trace ID observed at the edge is present at the origin.
- Check that child spans have the expected parent ID.
- Use stable
service.namevalues for the Worker, gateway, and each microservice. - For Honeycomb, verify that every span in the trace is written to one environment.
- For Datadog, verify that the chosen ingestion family supports the correlations and trace metrics your team expects.
8. Test with a known request
Send a request with a distinctive, non-sensitive marker that you can search for in the backend. Confirm the sequence from Cloudflare to Worker to origin to downstream service. Test an error and a slow request as well as a successful request; instrumentation or sampling mistakes often appear only on one path.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
9. Measure operational behavior before broad rollout
Observe ingest volume, sampling, query latency, retention, quotas, and resulting cost under realistic traffic. No universal retention period, quota, price, or performance benchmark applies across these products, so use the current plan terms for your account and region.
Choosing between Cloudflare-only, Datadog, and Honeycomb views
| Your question | Best first view | Why |
|---|---|---|
| Did a security rule, transformation, cache decision, route, or Worker affect this request? | Cloudflare Traces | It exposes the edge processing hierarchy and origin handoff. |
| Which application service, database call, or internal operation consumed the time? | Datadog or Honeycomb | Those systems can store spans emitted by your instrumented services. |
| Do we need one trace spanning edge and microservices? | Either backend, with shared OTLP export | The deciding factors are context propagation, instrumentation, and one common destination. |
| Do we want vendor-neutral ingestion and flexible attribute queries? | Honeycomb | It is built around OpenTelemetry ingestion and cross-dataset, high-dimensional queries within an environment. |
| Do we want tracing integrated with a broad existing observability platform? | Datadog | Its setup families integrate with Datadog’s wider APM and infrastructure workflows, subject to compatibility by ingestion path. |
Troubleshooting disconnected or incomplete traces
The origin appears, but its child services do not
First verify that the origin actually forwards W3C context on outbound calls. Then inspect each downstream service for header extraction and injection. A proxy, API gateway, messaging client, or custom HTTP wrapper can silently remove the headers. Add temporary logging of trace and span identifiers without recording sensitive payloads.
Free tools Windows power users keep installed
One-click scans. No signup required.
Cloudflare and the origin show different trace IDs
Confirm that Forward to origin is enabled and that the origin trusts the incoming context. Check for middleware that starts a new root span instead of continuing the extracted context. Also verify that a sampling decision or gateway policy is not intentionally creating a new trace.
Cloudflare data reaches the backend, but no combined trace appears
Check that Cloudflare and origin exporters point to the same logical Datadog intake or Honeycomb environment. In Honeycomb, an environment mismatch prevents a distributed trace from rendering correctly. In either backend, verify that an intermediary Collector has not rewritten or dropped trace identifiers.
Worker spans are missing
Confirm that Workers tracing is enabled for the Worker and that the request was eligible under the configured sampling rate. A Cloudflare request trace without Worker tracing will not automatically contain Worker-level spans.
Only some requests are searchable
Sampling and request selection determine what is recorded. Review the configured head-sampling rate, Cloudflare plan limits, backend sampling, and any Collector processors. A 5 percent example configuration should not be interpreted as evidence that 95 percent of requests are lost in every setup; actual behavior depends on the settings and products in your path.
Honeycomb queries show services but not one trace
Confirm that all participating spans use the same environment and preserve one trace ID. Check that each service has a stable service.name and that the Collector is not routing datasets into separate environments.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Datadog features differ from expectations
Identify which of Datadog’s four setup families you deployed. Consult its compatibility matrix for distributed tracing, trace metrics, and other required features. Direct OTLP ingestion and a Datadog distribution are not interchangeable from a feature-support perspective.
Operational and security decisions
Sampling is a diagnostic trade-off
Higher sampling improves the chance of finding a particular request but increases ingest volume and storage pressure. Lower sampling reduces overhead and cost but can hide rare failures. Consider separate policies for normal traffic, errors, and high-value routes where your tooling supports them, and document the policy so engineers know what an absent trace means.
Context is data that crosses a trust boundary
Accepting incoming trace context can allow an external caller to influence identifiers used in your telemetry. Decide whether Cloudflare should trust incoming headers or start a new context, and ensure that forwarding to the origin matches that decision. Never place secrets or personal data in trace attributes merely to make requests easier to find.
Retention and cost are implementation constraints
Cloudflare, Datadog, Honeycomb, and any Collector infrastructure can have different quotas, retention rules, and billing models. The available material does not establish universal prices, retention periods, or performance benchmarks. Evaluate current plan documentation using your expected request rate, span count, sampling policy, and required retention before production deployment.
Recommended architecture
For most teams, the cleanest design is to treat Cloudflare Traces as the edge specialist and Datadog or Honeycomb as the distributed-tracing system of record. Enable the Cloudflare features needed to inspect edge behavior, forward W3C context to a properly instrumented origin, and export both edge and application spans through OTLP to one destination. Keep service names and environments consistent, test trace continuity with known requests, and validate sampling, retention, quotas, and cost under realistic load.
Choose Datadog when its integrated APM and observability workflows outweigh the need for a provider-neutral setup, and verify feature support for your selected ingestion family. Choose Honeycomb when OpenTelemetry-first ingestion and high-dimensional investigation are the priority, while enforcing one environment for every span in a trace. In either case, the backend cannot recover spans that the origin never created or context that a downstream hop discarded.
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.
