Skip to content

Added note about possible errors if you don't follow the file naming … #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DominicCronin wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Added note about possible errors if you don't follow the file naming … #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,8 @@ Since an example is (sometimes) worth a thousand words, check out the 'example'
**Other useful info**
- The Logstash filter config files should follow a naming convention
(```[some-custom-label].filter.conf```).
They'll be loaded in alphabetical order.
They'll be loaded in alphabetical order. If you don't follow this convention, and the rspec tests don't pick up your files, you may see errors like this:
"LogStash::ConfigurationError: Expected one of #, input, filter, output at line 1, column 1"

- Logstash-tester assumes the patternsdir setting in grok filters is set to ```/etc/logstash/patterns```.

Expand Down