open-telemetry/opentelemetry-collector — reverse-engineered prompt

I want a working OpenTelemetry Collector style service from this repo that I can run locally and understand without digging through a bunch of internals.

Please make it act like a single telemetry pipeline that can receive traces, metrics, and logs, do some basic processing, and export them onward in a vendor neutral way. It should have a sensible default config, support the common formats mentioned in the docs like OTLP and the usual open source ecosystem, and be usable either as a lightweight agent on one machine or as a central collector.

Make the local developer experience smooth. I should be able to start it, send sample telemetry through it, and see that it is working with internal monitoring or clear logs. If anything is missing, add example configs and a simple demo flow so it feels runnable out of the box. Please keep it extensible and clean so custom receivers, processors, exporters, or extensions can be added later without touching core behavior.

Look up the current OpenTelemetry Collector docs online if you need to.