3 ms·
> It is a drop-in replacement for Elasticsearch if you are just ingesting data using APIs and searching using kibana (Kibana is not supported nor required with
by michaelmior 3y ago
> It is a drop-in replacement for Elasticsearch if you are just ingesting data using APIs and searching using kibana (Kibana is not supported nor required with OpenObserve. OpenObserve provides its own UI which does not require separate installation unlike kibana).
This seems contradictory. If OpenObserve doesn't support Kibana, how can it be a drop-in replacement for Elasticsearch queried using Kibana? Even if the OpenObserve UI has similar features, I can't just replace Elasticsearch with OpenObserve and keep the rest of my workflow the same, which I would consider a precondition to call something a drop-in replacement.
- vlovich123 3y agoSaid an alternate way, if Kibana drop in compat could be a thing, it would be easier for infra teams to do it as a drop in into existing stacks at bigger companies which makes it easier to steal market share of existing customers on the ES stack. There’s probably a non trivial amount of existing dashboards built and UX familiarity that would be a friction point without seamless compat. Is Kibana support totally out of the question?
- prabhatsharma 3y ago>Is Kibana support totally out of the question? Actually no. We already have a good amount of pieces in place to support kibana. 2-3 weeks of dev work and it will be ready. Just not the top priority right now though.
- vlovich123 3y agoWow that’s really cool. Great job!
- sscarduzio 3y agoI'm very interested in Kiban compat, what channel is the best for people like me to follow the progress towards this feature?
- prabhatsharma 3y agoEasiest way to interact with the team is to follow the github project (add to your watch) and join the slack community.