Files
telemetry/docs/vision.md
Tiffany HrabusaandGitHub 2a19d55c4c [docs] Clean up internal observability docs (#10454)
#### Description
Now that
[4246](https://github.com/open-telemetry/opentelemetry.io/pull/4246),
[4322](https://github.com/open-telemetry/opentelemetry.io/pull/4322),
and [4529](https://github.com/open-telemetry/opentelemetry.io/pull/4529)
have been merged, and the new [Internal
telemetry](https://opentelemetry.io/docs/collector/internal-telemetry/)
and
[Troubleshooting](https://opentelemetry.io/docs/collector/troubleshooting/)
pages are live, it's time to clean up the underlying Collector repo docs
so that the website is the single source of truth.

I've deleted any content that was moved to the website, and linked to
the relevant sections where possible. I've consolidated what content
remains in the observability.md file and left troubleshooting.md and
monitoring.md as stubs that point to the website.

I also searched the Collector repo for cross-references to these files
and adjusted links where appropriate.

~~Note that this PR is blocked by
[4731](https://github.com/open-telemetry/opentelemetry.io/pull/4731).~~
EDIT: #4731 is merged and no longer a blocker.

<!-- Issue number if applicable -->
#### Link to tracking issue
Fixes #8886
2024-06-28 10:25:13 +02:00

1.2 KiB

OpenTelemetry Collector Long-term Vision

The following are high-level items that define our long-term vision for OpenTelemetry Collector, what we aspire to achieve. This vision is our daily guidance when we design new features and make changes to the Collector.

This is a living document that is expected to evolve over time.

Performant

Highly stable and performant under varying loads. Well-behaved under extreme load, with predictable, low resource consumption.

Observable

Expose own operational metrics in a clear way. Be an exemplar of observable service. Allow configuring the level of observability (more or less metrics, traces, logs, etc reported). See more details.

Multi-Data

Support traces, metrics, logs and other relevant data types.

Usable Out of the Box

Reasonable default configuration, supports popular protocols, runs and collects out of the box.

Extensible

Extensible and customizable without touching the core code. Can create custom agents based on the core and extend with own components. Welcoming 3rd party contribution policy.

Unified Codebase

One codebase for daemon (Agent) and standalone service (Collector).