Adding OpenObserve as Export Destination for Logs
TLDR yuta inquired about adding OpenObserve as an export destination for their collector. Prabhat suggested using otel-collector for sending logs, metrics, and traces.
yuta
Tue, 20 Jun 2023 12:26:03 UTCsorry, I didn’t realize there was already a similar issue.
Prabhat
Tue, 20 Jun 2023 13:09:54 UTCYou could use otel-collector for sending logs (using elasticsearch exporter), metrics (using prometheus remote write) and traces (using OTLP)
yuta
Wed, 21 Jun 2023 01:19:15 UTCthanks! :grinning:
OpenObserve
Indexed 419 threads
OpenObserve is an open-source, petabyte-scale observability platform for the cloud native realm, offering a 10x cost reduction and 140x less storage use compared to competitors like Elasticsearch or Splunk. Built in Rust for exceptional performance, it offers comprehensive features like logs, metrics, traces, dashboards, and more | Knowledge Base powered by Struct.AI
View in App
yuta
Tue, 20 Jun 2023 03:45:06 UTCHello! Our organization is currently considering transitioning our observability backend from ElasticStack to OpenObserve. As such, we’re currently in the process of deploying OpenObserve on Kubernetes for testing in our development environment. We’ve been using the OpenTelemetry Collector to send traces, metrics, and logs to Elastic. Could you please advise us on how to add OpenObserve as an export destination for our collector? Upon checking the document (), I found that
For traces, we should use the otlphttp exporter
For metrics, we should use the prometheusremotewriteexporter
Which exporter should we use for logs?