What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The right tracing platform for Cloudflare Workers is the one that accepts Workers’ OpenTelemetry export, preserves enough context for your investigations, fits your sampling and retention budget, and does not leave your team assuming that Cloudflare spans automatically join backend traces. Start with a small deployed Worker, send representative traffic to the candidate destination, and verify the exact operations, attributes, and costs you will depend on.
Cloudflare provides built-in instrumentation for handler invocations, outbound fetch calls, bindings, and RPC calls. You can add custom spans for application work, but Workers tracing is still documented as an open beta, so span names, attributes, and coverage can change.
As an Amazon Associate I earn from qualifying purchases.
What a Cloudflare Workers tracing platform must do
Workers emits OpenTelemetry traces and logs to a configured destination. A platform is a practical candidate only if it can receive that export through the OpenTelemetry endpoint and display the data your team needs. Cloudflare names Honeycomb, Grafana Cloud, and Axiom as compatible examples; that is an interoperability example, not a ranking of their cost, interface, retention, or diagnostic quality.
Compatibility should be proven in your account rather than inferred from a vendor logo. A successful pilot should show a real Worker invocation, its child operations, the expected attributes, and the behavior of unsampled requests. Check the destination’s current OpenTelemetry ingestion requirements, authentication method, region, limits, and commercial terms directly before committing.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
| Decision area | What to verify |
|---|---|
| Ingestion | Whether the destination accepts the OpenTelemetry endpoint and configuration route required by Cloudflare, and whether a small deployment delivers usable traces. |
| Correlation | Whether trace IDs connect with your origin and other services. Cloudflare currently documents that IDs are not propagated to services outside Cloudflare. |
| Coverage | Whether handler, fetch, binding, RPC, custom application, routing, cache, and origin timing are represented as you expect. |
| Sampling | Whether head-based sampling is sufficient for your traffic and investigations, and how the rate affects destination volume. |
| Retention and billing | How the provider charges for ingestion and storage, how long it retains data, and how those terms compare with Workers’ seven-day retention. |
| Data control | Whether traces should remain persisted in Cloudflare as well as being exported, or whether the external platform should be the only stored destination. |
| Stability | Whether dashboards and queries can tolerate changes to beta span names and attributes. |
Turn on Workers tracing safely
Enable the built-in instrumentation
Cloudflare says Workers provides tracing instrumentation out of the box, with no code changes or SDK required. In Wrangler, enable observability.traces.enabled. A minimal configuration is conceptually:
[observability.traces]
enabled = true
head_sampling_rate = 1.0The documented default for head_sampling_rate is 1, meaning 100 percent of requests are sampled when you do not specify a rate. The valid range is 0 through 1. Choose a lower value deliberately for high-volume production traffic, then compare the captured volume with what your investigations require.
Cloudflare describes sampling as head-based: the decision is made at the start of the request. Workers does not currently provide tail-based sampling, so it cannot first observe an error or slow outcome and then decide to retain that request. If rare failures matter, a low rate can miss exactly the request you need; if volume matters more, a higher rate increases data and downstream cost.
Deploy and verify arrival
- Create and configure the external destination using the provider’s current OpenTelemetry instructions.
- Put the configured destination name into the Wrangler observability export configuration.
- Decide whether Cloudflare should retain a copy. The documented default is
persist: true; settingpersist: falsedisables Cloudflare persistence for telemetry that is exported externally. - Redeploy the Worker. Cloudflare notes that events can take several minutes to appear.
- Generate known traffic that exercises a handler, a
fetch, a binding, and any RPC path your application uses. Confirm that each expected operation appears in the destination. - Record the observed event rate, attributes, missing spans, arrival delay, and storage footprint before increasing traffic or changing the sampling rate.
The supported external OpenTelemetry types described by Cloudflare are traces and logs. Workers infrastructure metrics and custom metrics are outside this export path, so a tracing destination cannot replace your metrics pipeline.
Understand what Workers traces contain
Automatic runtime spans
Built-in instrumentation covers handler invocations, outbound fetch calls, binding operations, and RPC calls. This gives you a starting view of where a request spends time inside the Worker runtime. It does not mean every line of JavaScript or every internal runtime action receives a dedicated span.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Custom application spans
Custom spans let you mark business steps that automatic instrumentation cannot identify, such as parsing, authorization, a cache decision, or a particular database operation. Use them to expose meaningful boundaries rather than recording large payloads as attributes.
- Span names are truncated to 64 bytes.
- Each span has approximately 64 KB available for attributes and exception data.
- The cited Workers documentation does not provide manual parent-child wiring,
spanContext(), orsetStatus. - Do not design dashboards around oversized attribute values or assume that you can manually repair parentage with those APIs.
Keep custom names short, stable, and low-cardinality. Put identifiers needed for investigation in carefully selected attributes, and avoid secrets, tokens, request bodies, or unbounded user input.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTiming that can look incomplete
Cloudflare’s limitations documentation says non-I/O operations may report 0 ms because of runtime timing protections. A zero value therefore does not prove that application code consumed no CPU time. Compare the trace with logs, application timing, and request-level measurements before treating it as a performance conclusion.
Do not assume end-to-end trace joins
The documented Workers limitation is significant: trace IDs are not propagated to services outside Cloudflare. A Worker trace therefore may stop at the Cloudflare boundary instead of joining automatically to a trace from your origin, queue consumer, database service, or other backend.
Ask each candidate platform how it represents this break in context. A useful interface should make the Worker trace easy to pivot from using request identifiers, Ray IDs, timestamps, URL data, or an application-generated correlation value. Treat any apparent cross-service join as something to verify in your own deployment, not as a guaranteed consequence of enabling OpenTelemetry export.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
A practical correlation test
- Send a request through the Worker to a backend service that already emits traces.
- Capture the Worker trace identifier and the backend trace identifier independently.
- Check whether the destination presents one connected trace or two separate traces.
- If they are separate, test the request ID, Ray ID, or another deliberately logged correlation field as the pivot.
- Document the resulting workflow for on-call staff; do not promise automatic trace navigation if the platform cannot provide it.
Separate Workers tracing from Cloudflare-wide Traces
Cloudflare also documents a broader Traces view for production request paths. It can show supported Cloudflare steps such as routing, cache processing, Workers, and origin connections, and it supports filtering by Ray ID. This view is related to Worker tracing but is not the same as selecting an external OpenTelemetry destination.
Use the broader view when the question is “Where did this request go through Cloudflare?” Use the Worker trace when the question is “Which handler, fetch, binding, RPC, or custom application step was involved?” Some Cloudflare-wide operations have no dedicated span, so inspect the actual fields available for the request rather than expecting a span for every step.
The Cloudflare-wide documentation says request and query-string values are captured while header values are not. That affects both debugging and data exposure: a query parameter may be searchable, but a value carried only in a header may not appear in the trace view.
Choose sampling, retention, and persistence together
Sampling strategy
Start with the documented 100 percent default in a low-volume test environment so you can establish coverage. For production, select a head-sampling rate from 0 to 1 based on request volume, investigation frequency, and the destination’s ingestion terms. Measure the resulting number of spans and bytes rather than estimating from request count alone.
Because Workers’ decision is head-based, sampling cannot preferentially retain slow or failed requests after the fact. If those events are uncommon, compensate with application logs, explicit error signals, a higher rate on a diagnostic deployment, or a separate mechanism that does not depend on tail selection.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Cloudflare retention and the external platform
Workers traces are documented as retained for seven days. The external destination may retain data for a different period and may charge separately for ingestion, indexed fields, queries, or storage. Compare those terms before deciding that an external platform is your long-term archive.
Cloudflare states that persisted traces begin contributing to account-level ingestion and storage usage on December 1, 2026. That date is future-facing and time-sensitive relative to the October 2026 documentation context, so recheck the current Cloudflare terms before publication or a purchasing decision. If you set persist: false, the externally exported telemetry is not also persisted in Cloudflare; verify exactly which telemetry types that setting covers in your configuration.
Data residency and deletion
Ask where the destination stores data, how quickly it deletes a trace, and whether backups or derived indexes follow the same policy. Confirm whether sensitive attributes are redacted before export. These controls matter more when the external platform retains data longer than the seven-day Workers window.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Account for beta limitations and changing fields
Cloudflare labels Workers tracing as open beta. The limitations page warns that attributes are incomplete and that span and attribute names may change. Build dashboards with a compatibility layer: centralize field mappings, avoid hard-coding undocumented names, and test saved queries after Workers changes.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Keep a small synthetic request that exercises every span type your alerts depend on.
- Alert on missing event volume, not only on a particular span name.
- Version dashboards and queries so a field rename can be rolled back.
- Record the Worker runtime and deployment date alongside diagnostic exports.
Cloudflare’s FAQ says tracing has no measurable overhead on request processing and that requests not sampled skip tracing entirely. That is a vendor statement, not an independent benchmark. Validate latency and resource behavior with your own traffic, especially when adding custom spans or changing sampling.
A platform-selection checklist
Run this checklist against every candidate destination:
- Endpoint: Can it receive Cloudflare’s OpenTelemetry export using the required endpoint, credentials, and destination name?
- Evidence: Does a deployed Worker deliver handler, fetch, binding, RPC, log, and custom-span data within the expected delay?
- Correlation: Can investigators pivot when trace IDs stop at the Cloudflare boundary?
- Queries: Can the interface filter the fields you actually receive, including Ray ID or application correlation values?
- Sampling: Can you model head-based sampling at your peak request rate, and does the service offer the diagnostic controls you need without tail sampling?
- Retention: Does its retention and deletion behavior fit a seven-day Cloudflare source window and your compliance requirements?
- Cost: What are the current ingestion, indexing, query, and storage charges for your measured event volume?
- Data control: Is
persist: falseappropriate, and can you prove where the only retained copy lives? - Change tolerance: Can dashboards survive beta changes to names and attributes?
- Coverage gaps: Which operations have no dedicated span, and what other telemetry answers those questions?
A decision rule for common workloads
Small or low-volume Worker
Use a full-sampling pilot first. The priority is confirming ingestion and understanding the shape of automatic and custom spans before optimizing cost. Keep persistence enabled until you have proved that the external copy is complete and recoverable, unless your data policy requires otherwise.
High-volume public API
Estimate event and byte volume at several head-sampling rates, then test the rate that preserves useful coverage without overwhelming the destination. Pair traces with logs and metrics because Workers infrastructure metrics and custom metrics do not travel through this OpenTelemetry path.
Distributed application with an important origin
Make cross-boundary correlation the gating test. If trace IDs do not propagate outside Cloudflare, choose the destination and application conventions that make request IDs, Ray IDs, or timestamps reliable pivots. Reject any design that depends on an automatic end-to-end trace until your own test demonstrates it.
Teams investigating routing and cache behavior
Include Cloudflare-wide Traces and Ray ID lookup in the workflow evaluation. An external Worker trace alone may not answer questions about routing, cache, or origin timing, while the broader Cloudflare view may not expose every application operation.
Quick Recap
What to document before rollout
- Record the exact Wrangler settings, destination name, sampling rate, and persistence choice.
- Save representative trace examples for successful, failed, slow, fetch-heavy, binding-heavy, and RPC-heavy requests.
- List fields and span names used by dashboards, with an owner responsible for updating them when beta instrumentation changes.
- Write the fallback investigation path for requests that are not sampled or whose trace stops at the Cloudflare boundary.
- Recalculate retention and account-level ingestion implications before December 1, 2026, and whenever Cloudflare or the destination changes its terms.
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.
