Bug 209776 - [NEW PORT] Beats Ports for FreeBSD
Summary: [NEW PORT] Beats Ports for FreeBSD
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kurt Jaeger
URL:
Keywords: patch-ready
Depends on:
Blocks:
 
Reported: 2016-05-26 22:19 UTC by Riccardo Calixte
Modified: 2016-05-27 18:24 UTC (History)
2 users (show)

See Also:


Attachments
packetbeat.shar (4.16 KB, text/plain)
2016-05-27 04:24 UTC, Kurt Jaeger
no flags Details
filebeat.shar (4.15 KB, text/plain)
2016-05-27 04:25 UTC, Kurt Jaeger
no flags Details
packetbeat-1.2.3.shar (4.18 KB, text/plain)
2016-05-27 05:13 UTC, Kurt Jaeger
no flags Details
filebeat-1.2.3.shar (4.17 KB, text/plain)
2016-05-27 05:13 UTC, Kurt Jaeger
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Riccardo Calixte 2016-05-26 22:19:19 UTC
Opening this to track the creation of some of the ports for the Beats shippers for Elasticsearch (https://www.elastic.co/products/beats), in particular filebeat and packetbeat).
Comment 1 Riccardo Calixte 2016-05-26 23:16:45 UTC
Discussion on this started here: https://github.com/freebsd/freebsd-ports/pull/49
Comment 2 Kurt Jaeger freebsd_committer freebsd_triage 2016-05-27 04:24:48 UTC
Created attachment 170704 [details]
packetbeat.shar

Testbuilds are fine, portlint is fine.
Comment 3 Kurt Jaeger freebsd_committer freebsd_triage 2016-05-27 04:25:30 UTC
Created attachment 170705 [details]
filebeat.shar

testbuilds are fine, portlint is OK
Comment 4 Kurt Jaeger freebsd_committer freebsd_triage 2016-05-27 04:27:02 UTC
Now, has anyone run-tested those ports ? I have no operational experience with elasticsearch etc, so how do we know it's working ? Riccardo, did you run-test those ports ?
Comment 5 Kurt Jaeger freebsd_committer freebsd_triage 2016-05-27 05:13:07 UTC
Created attachment 170706 [details]
packetbeat-1.2.3.shar

newer version
Comment 6 Kurt Jaeger freebsd_committer freebsd_triage 2016-05-27 05:13:41 UTC
Created attachment 170707 [details]
filebeat-1.2.3.shar

updated version 1.2.3
Comment 7 Riccardo Calixte 2016-05-27 13:41:06 UTC
I've gotten filebeat working on both FreeBSD 9.3 and 10.1 (sorry it's not the latest). Compilation was smooth, pulled and installed all the source and dependencies necessary. Phenomenal thumbs up. Thanks for the quick turnaround!

As an aside, is this a model we can apply to the other Beats, either from Elastic or the community? I know each version bump would likely require testing, etc., but those of us with FreeBSD in production environments (i.e. at least me) will gladly contribute whatever time/work is necessary to keep these maintained and up-to-date.
Comment 8 Palle Girgensohn freebsd_committer freebsd_triage 2016-05-27 18:17:17 UTC
Committed. Thanks!
Comment 9 commit-hook freebsd_committer freebsd_triage 2016-05-27 18:17:33 UTC
A commit references this bug:

Author: girgen
Date: Fri May 27 18:16:42 UTC 2016
New revision: 415952
URL: https://svnweb.freebsd.org/changeset/ports/415952

Log:
  Add filebeat and packagebeat from Elastic

  Thanks to Kurt Jaeger and Riccardo Calixte for
  collaboration and testing.

  PR:     209776

Changes:
  head/sysutils/Makefile
  head/sysutils/filebeat/
  head/sysutils/filebeat/Makefile
  head/sysutils/filebeat/distinfo
  head/sysutils/filebeat/files/
  head/sysutils/filebeat/files/filebeat.in
  head/sysutils/filebeat/files/patch-libbeat_scripts_Makefile
  head/sysutils/filebeat/pkg-descr
  head/sysutils/filebeat/pkg-plist
  head/sysutils/packetbeat/
  head/sysutils/packetbeat/Makefile
  head/sysutils/packetbeat/distinfo
  head/sysutils/packetbeat/files/
  head/sysutils/packetbeat/files/packetbeat.in
  head/sysutils/packetbeat/files/patch-libbeat_scripts_Makefile
  head/sysutils/packetbeat/pkg-descr
  head/sysutils/packetbeat/pkg-plist
Comment 10 Kurt Jaeger freebsd_committer freebsd_triage 2016-05-27 18:24:34 UTC
(In reply to Riccardo Calixte from comment #7)
> As an aside, is this a model we can apply to the other Beats, either from 
> Elastic or the community?

From my point of view: yes. If you submit new Beats-related ports, please
submit them as shar files to bugs.freebsd.org -- your initial submission came via github. The github ports repo is mostly-read, so issues raised there are normally not easy to work with.