Add Sematext OTLP endpoints to documentation

[otisg]

Summary

Added Sematext and its endpoints for traces and logs

[cloudflare-docs-bot]

Review

⚠️ 1 warning found in commit 400ac37.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (1)

File

Issue

workers/observability/exporting-opentelemetry-data/index.mdx line 35

Missing OTLP signal path in endpoint URLs — The added Sematext row lists https://otlp-receiver.sematext.com and https://otlp-receiver.eu.sematext.com for both traces and logs, while every other provider row includes the per-signal path (/v1/traces and /v1/logs). OTLP/HTTP destinations require the full .../v1/traces and .../v1/logs URL, and the dashboard expects the exact endpoint, so users copying this value may fail to send telemetry. Fix: Use the full signal-specific URLs (for example https://otlp-receiver.sematext.com/v1/traces and .../v1/logs, plus the EU equivalents), consistent with the rest of the table, or confirm the exact path with Sematext's OTLP documentation and update accordingly.

Style Guide Review

✅ No style-guide issues found.

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.

[otisg]

Re /v1/traces and /v1/logs missing from this PR for Sematext. We actually allow people to send traces/logs/metrics to just the root URI as well, so that's why I provided that endpoint. If that's a problem from Cloudflare's side I can change the PR to specify the full /v1/traces and /v1/logs.