# Elastic Observability vs OpenTelemetry: Are We Finally on the "Right" Path?

**URL:** <https://discuss.elastic.co/t/elastic-observability-vs-opentelemetry-are-we-finally-on-the-right-path/385880>\
**Category:** Elastic Observability\
**Created:** [April 14, 2026, 12:01pm UTC](https://discuss.elastic.co/t/elastic-observability-vs-opentelemetry-are-we-finally-on-the-right-path/385880 "2026-04-14T12:01:22Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 22, 2026, 2:46pm UTC](https://discuss.elastic.co/t/elastic-observability-vs-opentelemetry-are-we-finally-on-the-right-path/385880/22 "2026-05-22T14:46:13Z")

</div>

I'll take a look  
I wouldn't be surprised  
OTOH funny. I've rarely built an ingest pipeline through the UI. I always do the code side because that's how I started and I like the simulation and some other things are super easy that way.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 22, 2026, 6:42pm UTC](https://discuss.elastic.co/t/elastic-observability-vs-opentelemetry-are-we-finally-on-the-right-path/385880/23 "2026-05-22T18:42:57Z")

</div>

I opened a feature / bug

> <https://github.com/elastic/kibana/issues/270761>
>
> \### What?
> 
> The setting for field\_access\_pattern for ingest pipeline is not avail…able in the UI used for creating or editing Ingest Pipelines. Stack Mgt -\> Ingest Pipeline -\> Create / Edit
> 
> This is a 9.2+ added capability.
> 
> https://www.elastic.co/docs/manage-data/ingest/transform-enrich/ingest-pipelines#access-source-pattern
> 
> 
> 
> 
> \### Why?
> 
> This is becoming increasingly important as more users onboard OTEL data with dotted field names they will need to be access the dotted field names. 
> 
> This setting should be available in the UI. 
> 
> 
> \### Acceptance Criteria
> 
> \_No response\_
> 
> \### Priority
> 
> Important (workaround exists)
> 
> \### Blocked By
> 
> \_No response\_
> 
> \### Additional Context
> 
> \_No response\_

---

<div class="post-metadata">

**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\
**Post date:** [August 20, 2026, 10:48am UTC](https://discuss.elastic.co/t/elastic-observability-vs-opentelemetry-are-we-finally-on-the-right-path/385880/24 "2026-08-20T10:48:12Z")

</div>

> **[Elastic Agent as OpenTelemetry Collector: One unified pipeline — Elastic...](https://www.elastic.co/observability-labs/blog/opentelemetry-collector-elastic-agent)**
>
> Elastic Agent 9.3 runs Beats and native OTel Collector pipelines in one agent. Existing configs, dashboards and integrations work without changes.

Just noticed this post. They mention here it is now possible to manage with Fleet. The version 9.3 seems a bit weird though...

[Previous page](https://discuss.elastic.co/t/elastic-observability-vs-opentelemetry-are-we-finally-on-the-right-path/385880.md?page=1)