Skip to content

Commit 67ac395

Browse files
artysidorenkoedsiper
authored andcommitted
output: elasticsearch: update ES plugin readme for Logstash_Prefix_Key (fluent#258)
Current documentation is unclear/incomplete - updated to explain how the Logstash_Prefix_Key configuration works.
1 parent 7d27745 commit 67ac395

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

output/elasticsearch.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The **es** output plugin, allows to flush your records into a [Elasticsearch](ht
2626
| Replace\_Dots | When enabled, replace field name dots with underscore, required by Elasticsearch 2.0-2.3. | Off |
2727
| Trace\_Output | When enabled print the elasticsearch API calls to stdout (for diag only) | Off |
2828
| Current\_Time\_Index | Use current time for index generation instead of message record | Off |
29-
| Logstash\_Prefix\_Key | Prefix keys with this string | |
29+
| Logstash\_Prefix\_Key | When included: the value in the record that belongs to the key will be looked up and over-write the Logstash\_Prefix for index generation. If the key/value is not found in the record then the Logstash\_Prefix option will act as a fallback. Nested keys are not supported (if desired, you can use the nest filter plugin to remove nesting) | |
3030

3131
> The parameters _index_ and _type_ can be confusing if you are new to Elastic, if you have used a common relational database before, they can be compared to the _database_ and _table_ concepts. Also see [the FAQ below](elasticsearch.md#faq-multiple-types)
3232

0 commit comments

Comments
 (0)