Fix asciidoc formatting for conversion to asciidoctor

Fixes #10744
This commit is contained in:
Karen Metts 2019-05-01 20:37:10 -04:00
parent 32934e6775
commit ec74c231d6
5 changed files with 7 additions and 9 deletions

View file

@ -168,7 +168,7 @@ modules:
var.input.azure_event_hubs.event_hubs:
- ["name", "initial_position", "storage_container", "decorate_events", "event_hub_connection"] <3>
- ["insights-operational-logs", "TAIL", "activity-logs1", "true", "Endpoint=sb://...EntityPath=insights-operational-logs"]
- ["insights-operational-logs", "TAIL", "activity_logs2",<4> "true", "Endpoint=sb://...EntityPath=insights-operational-logs"]
- ["insights-operational-logs", "TAIL", "activity_logs2", "true", "Endpoint=sb://...EntityPath=insights-operational-logs"] <4>
- ["insights-metrics-pt1m", "TAIL", "dbmetrics", "true", "Endpoint=sb://...EntityPath=insights-metrics-pt1m"]
- ["insights-logs-blocks", "TAIL", "dbblocks", "true", "Endpoint=sb://...EntityPath=insights-logs-blocks"]
- ["insights-logs-databasewaitstatistics", "TAIL", "dbwaitstats", "false", "Endpoint=sb://...EntityPath=insights-logs-databasewaitstatistics"]

View file

@ -134,7 +134,7 @@ curl -XGET 'localhost:9600/_node/pipelines/test?pretty'
Example response:
[source,json]
--------------------------------------------------
----------
{
"pipelines" : {
"test" : {
@ -145,7 +145,7 @@ Example response:
"config_reload_interval" : 3
}
}
------------------------------------------------
----------
If you specify an invalid pipeline ID, the request returns a 404 Not Found error.

View file

@ -8,7 +8,7 @@ can start adding custom code to process data with Logstash.
**Example Usage**
[source,sh]
--------------------------------------------
-------------------------------------------
bin/logstash-plugin generate --type input --name xkcd --path ~/ws/elastic/plugins
-------------------------------------------

View file

@ -24,7 +24,7 @@ Distributions like Debian Jessie, Ubuntu 15.10+, and many of the SUSE derivative
`systemctl` command to start and stop services. Logstash places the systemd unit files in `/etc/systemd/system` for both deb and rpm. After installing the package, you can start up Logstash with:
[source,sh]
--------------------------------------------
-------------------------------------------
sudo systemctl start logstash.service
-------------------------------------------
@ -34,7 +34,7 @@ sudo systemctl start logstash.service
For systems that use upstart, you can start Logstash with:
[source,sh]
--------------------------------------------
-------------------------------------------
sudo initctl start logstash
-------------------------------------------
@ -46,7 +46,7 @@ The auto-generated configuration file for upstart systems is `/etc/init/logstash
For systems that use SysV, you can start Logstash with:
[source,sh]
--------------------------------------------
-------------------------------------------
sudo /etc/init.d/logstash start
-------------------------------------------

View file

@ -54,7 +54,6 @@ POST _xpack/security/role/logstash_writer
]
}
---------------------------------------------------------------
<1> The cluster needs the `manage_ilm` privilege if
{ref}/getting-started-index-lifecycle-management.html[index lifecycle management]
is enabled.
@ -133,7 +132,6 @@ POST _xpack/security/role/logstash_reader
]
}
---------------------------------------------------------------
<1> If you use a custom Logstash index pattern, specify that pattern
instead of the default `logstash-*` pattern.