You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quickwit is a sub-second search & analytics engine designed to work natively on cloud storage for distributed tracing, logs and other search use cases. Quickwit natively supports the OpenTelemetry protocol to store traces and Jaeger UI by implementing the SpanReader interface of Jaeger's Remote Storage API. This allows users to store tracing data in Quickwit via OLTP; then query and visualize using Jaeger UI. We have a tutorial on how to use Jaeger with Quickwit
As of Quickwit 5.0, only the SpanReader part is implemented therefore Quickwit can be used as a drop-in replacement to a span storage backend.
Is it possible to add Quickwit to the list of additional storage backends in this Meta issue ?
Disclaimer: I work on Quickwit
The text was updated successfully, but these errors were encountered:
Quickwit is a sub-second search & analytics engine designed to work natively on cloud storage for distributed tracing, logs and other search use cases. Quickwit natively supports the OpenTelemetry protocol to store traces and Jaeger UI by implementing the SpanReader interface of Jaeger's Remote Storage API. This allows users to store tracing data in Quickwit via OLTP; then query and visualize using Jaeger UI. We have a tutorial on how to use Jaeger with Quickwit
As of Quickwit 5.0, only the SpanReader part is implemented therefore Quickwit can be used as a drop-in replacement to a span storage backend.
Is it possible to add Quickwit to the list of additional storage backends in this Meta issue ?
Disclaimer: I work on Quickwit
The text was updated successfully, but these errors were encountered: