kibana

Kibana is once again Open Source, as of 2 months ago. https://github.com/elastic/kibana/blob/main/LICENSE.txt

https://github.com/elastic/kibana/tree/main/x-pack%2Fplugins... one I saw recently, obvs not the only one

I really love this tool - We use it to backport commits from master to our older release branches on the Kibana project. I can't emphasize enough how many hours this saves us every week. It creates a PR for each backport you make and label them "backport", so you can easily see them all here: https://github.com/elastic/kibana/pulls?q=is%3Apr+is%3Aopen+...

react-router depends on the ReactTraining/history package for browser navigation support. On 10 June 2017, an mind-bogglingly ill-conceived pull request[1] was merged, which causes invalid URLs to be pushed to the browser history, breaking the back button and page refresh in many scenarios. Ever since, users have practically been begging the maintainer to fix the bug[2] and implementing hacky workarounds[3]. In a twist of irony, the contributor who originally introduced the bug has: a) switched their own competing router package to a different history implementation[4] b) argued that fixing the bug (which was introduced in a patch release) would require a major version bump, implying it would be better to let it remain broken[5]. I concede that the software is open source, and nobody is entitled to make any demands of the maintainers. Nev

I will have to relook at this - the comment is from a year ago when they weren't using React. On a cursory look, it still seems to use a Node.JS based server [1]. One of the key side effects of needing a server is that there is a more involved distribution + installation process. You just can't run it on a static server like github pages or as a browser extension. [1] https://github.com/elastic/kibana/search?utf8=%E2%9C%93&q=ha...

>built with server side page rendering techniques (I am looking at you, Kibana). I'm not sure if this is actually accurate: 1. https://github.com/elastic/kibana/search?utf8=&q=React 2. https://elastic.github.io/eui

Kibana has quite a few rough edges but it takes non-technical users very far in terms of data exploration. Local setup also alleviates privacy concerns. The bummer is import/export: 'Upload CSV' feature has been almost introduced in 5.0 release but removed in the end [1], and CSV export has been asked for many times [2] but is still not there. So a user-friendly fork might be a worthy business idea. [1]: https://github.com/elastic/kibana/pull/8497 [2]: https://github.com/elastic/kibana/issues/1992

Something like ^\s*(:\+1:|\+\d+)\s*\!*\s*$ Even something as simple as this would clean up most of threads like these: https://github.com/elastic/kibana/issues/1084

There are also some serious unresolved issues in the current versions of the ELK stack bits, such as https://github.com/elastic/kibana/issues/5170, https://github.com/elastic/kibana/issues/1961, https://github.com/elastic/logstash/issues/3440. Even with all that though, it's still an incredibly useful tool for log analysis. It's a much different scenario than what one would use statsd, graphite, etc. for.

Kibana is a pretty big one: https://github.com/elastic/kibana

i don't know if this will be too confusing for you if you're new to sinatra, but the new version of Kibana (which is basically an interface to elasticsearch) uses sinatra, angular and grunt. Basically there are some grunt tasks to package it up into jruby so the final app runs wherever java is installed. https://github.com/elasticsearch/kibana

Kibana https://github.com/elasticsearch/kibana is an alternative.

Easiest way for me to learn Elasticsearch was through queries generated by Kibana [1] and playing with them inside Sense [2]. Kibana relies on Facets, version elasticsearch 1.0 introduces Aggregations, I would suggest using aggregations for your projects. [1] https://github.com/elasticsearch/kibana [2] https://chrome.google.com/webstore/detail/sense/doinijnbnggo...