Skip to content

docs: fix central config preview status and RUM/EDOT Browser contradiction #659

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
alexandra5000 wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −2
Draft

docs: fix central config preview status and RUM/EDOT Browser contradiction #659

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/reference/compatibility/features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ The following table shows Elastic features and their level of support and compat
| Usage of [Time Series Data Streams] | [Compatible] | [Supported] |
| **Central Management** | [Incompatible] | [Not supported] |
| Central management of OTel collectors | [Incompatible] | [Not supported] |
| Central management of OTel SDKs | [Compatible] | [Supported] |
| Central management of OTel SDKs | [Compatible]^5^ | [Supported]^5^ |


^1^ Refer to [limitations on host metrics](limitations.md#infrastructure-and-host-metrics)
Expand All @@ -50,6 +50,8 @@ The following table shows Elastic features and their level of support and compat

^4^ While ingesting traces that have been sampled using TBS is technically possible, there are important limitations to consider. Refer to [Tail-based sampling (TBS) limitations](../compatibility/limitations.md#tail-based-sampling-tbs) for more information.

^5^ Available as Technical Preview on {{stack}} 9.1+. Not available on {{serverless-full}}.

[Incompatible]: nomenclature.md
[Compatible]: nomenclature.md
[Not supported]: nomenclature.md
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/compatibility/limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ While {{edot}} and OTel-native data collection already covers most of the core O

{{edot}} already supports most core observability use cases, but in some scenarios, you may prefer to use classic Elastic ingestion components, such as {{agent}} ({{product.fleet}}-managed), {{product.apm-agent}} or {{product.apm-server}}:

* **Real user monitoring (RUM):** RUM ingestion and visualizations are not yet available for OTel-native data.
* **Real user monitoring (RUM):** [EDOT Browser](elastic-otel-rum-js://reference/edot-browser/index.md) is available as Technical Preview for OTel-native browser instrumentation. For production RUM, continue using the classic Elastic {{product.apm}} [browser agent](apm-agent-rum-js://reference/index.md).
* **Universal profiling:** This capability is currently only supported in the classic stack.
* **Existing integrations and dashboards:** Many prebuilt Elastic integrations and dashboards are designed for ECS-formatted data and may not work as expected with the OpenTelemetry semantic conventions without customization.
* **Managed processing of logs:** Elastic doesn't provide curated, centralized {{es}} ingest pipelines for OTel-native data. Process logs in the Collector instead, or define your own ingest pipeline. Refer to [Centralized parsing and processing of data](#centralized-parsing-and-processing-of-data) for more information.
Expand Down
Loading