github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 22:57:16 -04:00
Code Issues Projects Releases Packages Wiki Activity

Fixed links and foramtting

Browse source 
Fixes #5905
This commit is contained in:
DeDe Morton 2016-09-13 13:47:50 -07:00
parent cbc5f7ef24
commit 23edef94f0
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/static/breaking-changes.asciidoc vendored
View file

@ -10,9 +10,9 @@ after installing it via a package (RPM, DEB).
**Release Packages:** When Logstash is installed via DEB, RPM packages, it uses `/usr/share/logstash` and `/var/lib/logstash` to install binaries and config files **Release Packages:** When Logstash is installed via DEB, RPM packages, it uses `/usr/share/logstash` and `/var/lib/logstash` to install binaries and config files
respectively. Previously it used to install in `/opt` directory. This change was done to make the user experience respectively. Previously it used to install in `/opt` directory. This change was done to make the user experience
consistent with other Elastic products. Full directory layout is described https://www.elastic.co/guide/en/logstash/5.0/dir-layout.html[here]. consistent with other Elastic products. Full directory layout is described in <<dir-layout>>.
**Command Line Interface:** Most of the long form https://www.elastic.co/guide/en/logstash/5.0/command-line-flags.html[options] have been renamed **Command Line Interface:** Most of the long form <<command-line-flags,options>> have been renamed
to adhere to the yml dot notation to be used in the settings file. Short form options have not been changed. to adhere to the yml dot notation to be used in the settings file. Short form options have not been changed.
**Plugin Manager Renamed:** `bin/plugin` has been renamed to `bin/logstash-plugin`. This change was to mainly prevent `PATH` being polluted when **Plugin Manager Renamed:** `bin/plugin` has been renamed to `bin/logstash-plugin`. This change was to mainly prevent `PATH` being polluted when

2
docs/static/deploying.asciidoc vendored
View file

@ -63,7 +63,7 @@ nodes. By default, Logstash uses the HTTP protocol to move data into the cluster
You can use the Elasticsearch HTTP REST APIs to index data into the Elasticsearch cluster. These APIs represent the You can use the Elasticsearch HTTP REST APIs to index data into the Elasticsearch cluster. These APIs represent the
indexed data in JSON. Using the REST APIs does not require the Java client classes or any additional JAR indexed data in JSON. Using the REST APIs does not require the Java client classes or any additional JAR
files and has no performance disadvantages compared to the transport or node protocols. You can secure communications files and has no performance disadvantages compared to the transport or node protocols. You can secure communications
that use the HTTP REST APIs by using {shield}[{security}], which supports SSL and HTTP basic authentication. that use the HTTP REST APIs by using {xpack}/xpack-security.html[{security}], which supports SSL and HTTP basic authentication.
When you use the HTTP protocol, you can configure the Logstash Elasticsearch output plugin to automatically When you use the HTTP protocol, you can configure the Logstash Elasticsearch output plugin to automatically
load-balance indexing requests across a load-balance indexing requests across a