Date: Tue, 10 Mar 2026 18:56:49 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 290979] [NEW PORT] textproc/kibana9: Browser based analytics and search interface to Elasticsearch Message-ID: <bug-290979-7788-XYQ1B6jwOd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-290979-7788@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290979 --- Comment #12 from Saro <web@saromedia.com> --- (In reply to Vladimir Druzenko from comment #11) I believe they (Kibana, Beats, Elastic Agent, Logstash, ml-cpp) all follow Elasticsearch release & versioning cycles. Elastic officially recommends keeping all ELK stack components on the same version, e.g. ES 9.2.6 == Kibana 9.2.6 == Logstash 9.2.6 == etc. (mainly for ES and Kibana). The ingest components (Logstash, Beats) are a bit less restrictive in this regard. See: https://www.elastic.co/support/matrix ("Product Compatibility") They do allow the minor version to be -/+ releases to facilitate upgrades of course. A warning will be logged when a deviation occurs. There used to be a doc page explaining this, but I am unable to find it now. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-290979-7788-XYQ1B6jwOd>