Logstash is an open source, server-side data processing pipeline that
ingests data from a multitude of sources simultaneously, transforms it,
and then sends it to your favorite "stash."
To start logstash as an agent during startup, add
logstash_enable="YES"
to your /etc/rc.conf.
Extra options can be found in startup script.
WARNING: In order for logstash to work properly,
you need /proc filesystem mounted.
sysutils/logstash7: Update 7.17.11 => 7.17.29, deprecate
Release Notes:
https://www.elastic.co/guide/en/logstash/7.17/releasenotes.html
Improve port:
- Replace PORTVERSION with DISTVERSION.
- Add LOCAL/vvd/elastic to MASTER_SITES for those who can't download
due to the HTTP error "Forbidden 403".
- Deprecate with date 2026-06-30 due to 7.x reached EoL on 15 Jan 2026.
- Limit JAVA_VERSION to supported 17, 11 and 8.
- Parametrize "logstash" with "${PORTNAME}".
- Adjust CONFLICTS.
- Add possibility to use custom user/group.
- Merge CHMODs.
- Fix white characters and remove unnecessary empty lines.
- Remove unnecessary MKDIR.
PR: 293746
Approved by: elastic (maintainer, implicit - inactive for more than 6 months)
MFH: 2026Q1
Mk/**java.mk: Convert bsd.java.mk to USES
The following features have been added or changed:
- Instead of USE_JAVA use USES=java. This defaults to
USES=java:build,run if NO_BUILD is undefined. Else it defaults to
USES=java:run
- Instead of USE_ANT=yes use USES=java:ant which also implies
USES=java:build
- Instead of JAVA_BUILD=yes use USES=java:build. Does not imply run or
extract
- Instead of JAVA_EXTRACT=yes use USES=java:extract does not imply
build or run
- Instead of JAVA_RUN=yes use USES=java:run does not imply extract or
build
- Instead of USE_JAVA=<version> use USES=java and JAVA_VERSION=<version>
Approved by: mat (portmgr), glewis
Differential Revision: https://reviews.freebsd.org/D48201
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
*/*: Remove redundant '-[0-9]*' from CONFLICTS
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Many CONFLICTS definitions used patterns like "bash-[0-9]*" to filter
for the bash package in any version. But that pattern is functionally
identical with just "bash".
Approved by: portmgr (blanket)
Fix spelling mistakes, typos, poor wording, hyphenation, jargonisms,
contractions, "<portname> is ..." cases, missing Oxford commas, and
other miscellaneous style bugs in the COMMENT line.
sysutils/logstash7: Update to 7.9.3
Changelog for 7.9.3:
* Notable issues fixed:
- Pipeline execution fixes to flushing and shutdown:
- Fix to stop inputs upon a worker error before terminating the pipeline
* Plugins:
- File Input - 4.2.2
- Fix: sincedb_clean_after not being respected
- Snmp Input - 1.2.7
- Added integration tests to ensure SNMP server and IPv6 connections
- Docs: example on setting IPv6 hosts
- Twitter Input - 4.0.3
- Fix: broken proxy configuration
- Fix: user rest api call + proxy configuration
PR: 250605
Submitted by: Juraj Lutter <juraj@lutter.sk>
sysutils/logstash7: Update to 7.9.2
Changelog since 7.9.1:
* Notable issues fixed
- Secret store thread safety issues with multiple pipelines
- Since 7.8.0, a change to optimise the speed of loading variables from
the Logstash Secret Store could cause Logstash not to be able to start
when the feature was used in conjunction with multiple pipelines.
- App Search output startup failure
- Since 7.9.0, a regression was introduced which prevented pipelines
using the Elastic App Search output from starting.
* Compatibility notice: Logstash and JDK 15
- Logstash is not yet compatible with JDK 15.
- While we are working to support JDK 15, we encourage you to use
supported
JDK versions (8, 11 or 14). See Java (JVM) version for details and the
(Only the first 15 lines of the commit message are shown above )
sysutils/logstash7: Update to version 7.9.1
Changelog:
* Notable issues fixed:
- Fixes in Docker image configuration of Monitoring and Central
Management:
- As more and more users adopt our docker images, we've been getting
reports on gaps where these images don't provide all the configuration
knobs the other artifacts do. This release exposes more environment
variables for configuring proxy support and certificate verification
mode for monitoring and central management , and for configuring
verification_mode
- Pipeline execution fixes to flushing and shutdown
- Since 7.2.0, a change caused terminating pipelines to not request
input plugins to cleanup before shutdown, which could cause leaks in
(Only the first 15 lines of the commit message are shown above )
