From 2df85a69fb01176a13d4e297b1f823834bf80c7c Mon Sep 17 00:00:00 2001 From: Mirko Bez Date: Thu, 25 May 2023 14:05:09 +0200 Subject: [PATCH] Update monitoring-apis.asciidoc Remove note that no longer applies given that api.http.port is now a range between port 9600 to port 9700 --- docs/static/monitoring/monitoring-apis.asciidoc | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/static/monitoring/monitoring-apis.asciidoc b/docs/static/monitoring/monitoring-apis.asciidoc index 0f7b7cf0049..bc832b94b6f 100644 --- a/docs/static/monitoring/monitoring-apis.asciidoc +++ b/docs/static/monitoring/monitoring-apis.asciidoc @@ -30,10 +30,6 @@ Example response: } -------------------------------------------------- -NOTE: By default, the monitoring API attempts to bind to `tcp:9600`. If this port is already in use by another Logstash -instance, you need to launch Logstash with the `--api.http.port` flag specified to bind to a different port. See -<> for more information. - [discrete] [[monitoring-api-security]] ==== Securing the Logstash API