Bug 200653 - New port: textproc/kibana4 Kibana 4 a remade Browser based analytics and search interface to ElasticSearch
Summary: New port: textproc/kibana4 Kibana 4 a remade Browser based analytics and sear...
Status: Closed DUPLICATE of bug 200582
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-05 11:05 UTC by setjmp
Modified: 2015-06-19 22:01 UTC (History)
2 users (show)

See Also:


Attachments
shar file of the completed port. (320.33 KB, text/plain)
2015-06-05 11:05 UTC, setjmp
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description setjmp 2015-06-05 11:05:02 UTC
Created attachment 157432 [details]
shar file of the completed port.

Kibana 4 is a whole new Kibana from elastic.co, running under node, with full webservices.

It makes a great dashboard with many graphing features for looking at elasticsearch indexes. One of it's main uses is with logstash generated elasticsearch indices.

It is entirely different from the kibana (version 3) port, and can function in addition to that one as well. I will have 4.1.0 ready to update this when it's released to, however at the moment the distfile changes daily. That port will trim the rc file a little too, as it includes log support, where as 4.0.2 outputs log to stdout, so was simple redirected to a file.
Comment 1 Michael Zhilin freebsd_committer freebsd_triage 2015-06-05 12:58:59 UTC
Hi

At first, thank you for your patch! 

I've noticed that it's already second ticket about kibana4 (first is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200582). 

Dear committers, 

Please have a look at these tickets, it's cool tool wanted by many freebsd users.

Thanks!
Comment 2 setjmp 2015-06-05 17:41:21 UTC
I think Sergey's submission looks great and he posted it first. I did it rapid as I am switching back to FreeBSD after sometime primarily a Windows desktop; and need all my tools going well. So I will have more to come; some with newer versions, more options which I need, etc. Hopefully useful for others as well.

Even the kibana, I'm already using a derivitive of my submission which is the current development version (4.1.0); which would require a new "make makesum" every night at the moment; and not good for the ports.

It might go well to cancel this submission so the other one makes it into the ports without slow. Just a thought.

Eric
Comment 3 Jason Unovitch freebsd_committer freebsd_triage 2015-06-11 01:42:01 UTC
Thanks!  There are few items to point out with the submission.

1.  `portlint -Ac` shows the following.
# portlint -Ac
FATAL: Makefile: [22]: use a tab (not space) after a variable name
1 fatal error and 0 warnings found.

2.  Testing must be performed.  A 'poudriere testport' log is preferred however see the Porter's Handbook for an acceptable alternative.
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-testing.html

In the future, check for pre-existing PRs before you open a new one.  Being that this is a duplicate, it doesn't make sense to duplicate the effort when it would be best to work together.  The other submission was portlint clean and had testing logs.  The biggest hold up would be the recently announced security advisory for an XSS attack in 4.0.0, 4.0.1, and 4.0.2.  That would have to be addressed before Kibana 4 could go in the tree.  See the link below for more details.
https://discuss.elastic.co/t/kibana-cross-site-scripting-vulnerability-cve-2015-4093/2258

Perhaps you can close this PR and offer your assistance updating PR #200582 for version 4.0.3.
Comment 4 setjmp 2015-06-19 21:56:54 UTC
Actually 4.1.0 is now released and much value added as well. Sorry I have been off of this for a few days and looking closer now at the other port which was pretty good too. Sorry, just thought my last might have gotten this one closed. Though may update with 4.1.0 here instead with the portlint adjustment. I actually use 4.1.0 here from a custom port already as I need it. The 4.0.2 was more to get it started and then 4.1.0 when the release happened and the distfiles wouldn't change.
Comment 5 setjmp 2015-06-19 22:01:22 UTC

*** This bug has been marked as a duplicate of bug 200582 ***