opendev/system-config
Code Issues Proposed changes

Enhancing logstash docs for adding new files

Browse Source 
Adding some extra verbiage to the docs to better explain how
the message tags tie in to telling logstash how to parse things.
Also noting which file to edit when adding new files, how to add
new parsing patterns, and some troubleshooting tips.

Change-Id: Ie91effd4b3ff3627ec040eb5c54b972e82add0e7
This commit is contained in:
pcrews 2014-08-02 12:57:34 -07:00
parent 64aa651bb4
commit c7ae1e3a5e
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/logstash.rst
View File

@ -165,6 +165,22 @@ The config file that tells Logstash how to do this flattening can be
found at
:file:`modules/openstack_project/templates/logstash/indexer.conf.erb`
This works via the tags that are associated with a given message.
The tags in
:file:`modules/openstack_project/templates/logstash/indexer.conf.erb`
are used to tell logstash how to parse a given file's messages, based
on the file's message format.
When adding a new file to be indexed to
:file:`modules/openstack_project/files/logstash/jenkins-log-client.yaml`
at least one tag from the indexer.conf.erb file should be associated
with the new file. One can expect to see '{%logmessage%}' instead of
actual message data if indexing is not working properly.
In the event a new file's format is not covered, a patch for
:file:`modules/openstack_project/templates/logstash/indexer.conf.erb`
should be submitted with an appropriate parsing pattern.
ElasticSearch
-------------