Looking for a suggested "default" backend when using OTLP exporters

[svrnm]

More and more languages provide support for metrics & logs, our current documentations for exporters recommend jaeger to verify OTLP for traces, but right now there is no immediate option for logs & metrics. We could suggest that people setup a collector and look at their telemetry with a logging exporter, but it would be nice to have something visual like open-telemetry/oteps#230 suggests.

for reference: #3144 (comment)

[cijothomas]

Our demo uses opensearch for logs. We can use that?
https://github.com/open-telemetry/opentelemetry-demo/tree/main/src/opensearch

And prom/grafana for metrics (demo already use that).

[svrnm]

yeah, we can update for OpenSearch, I think when I created the discussion there was no OTLP yet for OpenSearch?

[cijothomas]

to verify OTLP

if the goal is to just verify that OTLPExporter is setup correctly and it works, then collector with stdout/debug exporter is sufficient IMHO!
If the intent is more than that, there is no single tool today, so a combination of jaeger/opensearch/prom+grafana might be the best bet and is followed in demo already.

[svrnm]

Yes, for pure verficiation it's fine, but what many end-users want is something visual. We anticipate that in our docs already, e.g. here for JS:

https://opentelemetry.io/docs/languages/js/exporters/

By adding OpenSearch we have at least one OTLP endpoint per signal.

[cartermp]

I would say prometheus for metrics, for logs I'm unsure (and unopinionated right now). OpenSearch isn't bad as per @cijothomas's suggestion?

[svrnm]

So, I looked into the OpenSearch documentation and the basic setup is already ... complicated:

https://opensearch.org/docs/latest/quickstart/

If we compare that to jaeger & prometheus where one simply starts an "all-in-one" docker container, this is a lot of effort for quickly taking a look at your metrics.

I have no idea about OpenSearch but maybe there is an equivalent where I can get a single container up and running?