Skip to content

Commit

Permalink
Remove the HTTP endpoint from configuration (#4615)
Browse files Browse the repository at this point in the history 
The monitoring feature is not ready yet, so we decided to leave the
HTTP endpoint undocumented for now.
  • Loading branch information
@tsg @andrewkroh
tsg authored and andrewkroh committed Jul 5, 2017
1 parent 1fa64ba commit dd063d0
Show file tree
Hide file tree
Showing 7 changed files with 7 additions and 98 deletions.
15 changes: 1 addition & 14 deletions auditbeat/auditbeat.reference.yml
View file
Expand Up @@ -677,7 +677,7 @@ output.elasticsearch:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

Expand Down Expand Up @@ -729,19 +729,6 @@ setup.kibana:



#================================ HTTP Endpoint ======================================
# Each beat can expose internal data points through a http endpoint. For security
# reason the endpoint is disabled by default. This feature is currently in beta.

# Defines if http endpoint is enabled
#http.enabled: false

# Host to expose the http endpoint to. It is recommended to use only localhost.
#http.host: localhost

# Port on which the http endpoint is exposed. Default is 5066
#http.port: 5066

#================================ Logging ======================================
# There are three options for the log output: syslog, file, stderr.
# Under Windows systems, the log files are per default sent to the file output,
Expand Down
15 changes: 1 addition & 14 deletions filebeat/filebeat.reference.yml
View file
Expand Up @@ -1065,7 +1065,7 @@ output.elasticsearch:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

Expand Down Expand Up @@ -1117,19 +1117,6 @@ setup.kibana:



#================================ HTTP Endpoint ======================================
# Each beat can expose internal data points through a http endpoint. For security
# reason the endpoint is disabled by default. This feature is currently in beta.

# Defines if http endpoint is enabled
#http.enabled: false

# Host to expose the http endpoint to. It is recommended to use only localhost.
#http.host: localhost

# Port on which the http endpoint is exposed. Default is 5066
#http.port: 5066

#================================ Logging ======================================
# There are three options for the log output: syslog, file, stderr.
# Under Windows systems, the log files are per default sent to the file output,
Expand Down
15 changes: 1 addition & 14 deletions heartbeat/heartbeat.reference.yml
View file
Expand Up @@ -832,7 +832,7 @@ output.elasticsearch:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

Expand Down Expand Up @@ -884,19 +884,6 @@ setup.kibana:



#================================ HTTP Endpoint ======================================
# Each beat can expose internal data points through a http endpoint. For security
# reason the endpoint is disabled by default. This feature is currently in beta.

# Defines if http endpoint is enabled
#http.enabled: false

# Host to expose the http endpoint to. It is recommended to use only localhost.
#http.host: localhost

# Port on which the http endpoint is exposed. Default is 5066
#http.port: 5066

#================================ Logging ======================================
# There are three options for the log output: syslog, file, stderr.
# Under Windows systems, the log files are per default sent to the file output,
Expand Down
15 changes: 1 addition & 14 deletions libbeat/_meta/config.reference.yml
View file
Expand Up @@ -618,7 +618,7 @@ output.elasticsearch:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

Expand Down Expand Up @@ -670,19 +670,6 @@ setup.kibana:



#================================ HTTP Endpoint ======================================
# Each beat can expose internal data points through a http endpoint. For security
# reason the endpoint is disabled by default. This feature is currently in beta.

# Defines if http endpoint is enabled
#http.enabled: false

# Host to expose the http endpoint to. It is recommended to use only localhost.
#http.host: localhost

# Port on which the http endpoint is exposed. Default is 5066
#http.port: 5066

#================================ Logging ======================================
# There are three options for the log output: syslog, file, stderr.
# Under Windows systems, the log files are per default sent to the file output,
Expand Down
15 changes: 1 addition & 14 deletions metricbeat/metricbeat.reference.yml
View file
Expand Up @@ -1056,7 +1056,7 @@ output.elasticsearch:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

Expand Down Expand Up @@ -1108,19 +1108,6 @@ setup.kibana:



#================================ HTTP Endpoint ======================================
# Each beat can expose internal data points through a http endpoint. For security
# reason the endpoint is disabled by default. This feature is currently in beta.

# Defines if http endpoint is enabled
#http.enabled: false

# Host to expose the http endpoint to. It is recommended to use only localhost.
#http.host: localhost

# Port on which the http endpoint is exposed. Default is 5066
#http.port: 5066

#================================ Logging ======================================
# There are three options for the log output: syslog, file, stderr.
# Under Windows systems, the log files are per default sent to the file output,
Expand Down
15 changes: 1 addition & 14 deletions packetbeat/packetbeat.reference.yml
View file
Expand Up @@ -1070,7 +1070,7 @@ output.elasticsearch:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

Expand Down Expand Up @@ -1122,19 +1122,6 @@ setup.kibana:



#================================ HTTP Endpoint ======================================
# Each beat can expose internal data points through a http endpoint. For security
# reason the endpoint is disabled by default. This feature is currently in beta.

# Defines if http endpoint is enabled
#http.enabled: false

# Host to expose the http endpoint to. It is recommended to use only localhost.
#http.host: localhost

# Port on which the http endpoint is exposed. Default is 5066
#http.port: 5066

#================================ Logging ======================================
# There are three options for the log output: syslog, file, stderr.
# Under Windows systems, the log files are per default sent to the file output,
Expand Down
15 changes: 1 addition & 14 deletions winlogbeat/winlogbeat.reference.yml
View file
Expand Up @@ -647,7 +647,7 @@ output.elasticsearch:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

Expand Down Expand Up @@ -699,19 +699,6 @@ setup.kibana:



#================================ HTTP Endpoint ======================================
# Each beat can expose internal data points through a http endpoint. For security
# reason the endpoint is disabled by default. This feature is currently in beta.

# Defines if http endpoint is enabled
#http.enabled: false

# Host to expose the http endpoint to. It is recommended to use only localhost.
#http.host: localhost

# Port on which the http endpoint is exposed. Default is 5066
#http.port: 5066

#================================ Logging ======================================
# There are three options for the log output: syslog, file, stderr.
# Under Windows systems, the log files are per default sent to the file output,
Expand Down

0 comments on commit dd063d0

Please sign in to comment.