Skip to content
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.

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

Filebeat Syslog dashboard cannot be loaded if the grok expressions cannot be matched to a pattern. #3913

Closed
bohyun-e opened this issue Apr 5, 2017 · 1 comment
Labels

Comments

@bohyun-e
Copy link

bohyun-e commented Apr 5, 2017

Using 5.3 on Mac OS X

Running the system Filebeat module, all of my syslogs fail to match the expected message pattern. The built-in syslog dashboard does not load as a result of this.
image
This is the expected pattern:
"patterns": [ """%{SYSLOGTIMESTAMP:system.syslog.timestamp} %{SYSLOGHOST:system.syslog.hostname} %{DATA:system.syslog.program}(?:\[%{POSINT:system.syslog.pid}\])?: %{GREEDYMULTILINE:system.syslog.message}"""

Per @andrewkroh, to reproduce, run the following POST request:

POST _ingest/pipeline/filebeat-5.3.0-system-syslog-pipeline/_simulate { "docs": [ { "_source": { "message": "Apr 4 03:39:57 --- last message repeated 1 time ---" } } ] }

From the built-in dashboard, there are absolutely no errors exposed and the user does not immediately know why the Filebeat module is not working. Just by glimpsing at Discover tab in Kibana, it seems like everything is working but combined with the issue #3912, the user does not get any warnings or error messages exposed from Kibana dashboard or from the Filebeat logs (the logs report no errors)

image

cc: @tsg

@bohyun-e bohyun-e added the Filebeat Filebeat label Apr 5, 2017
@bohyun-e bohyun-e changed the title Filebeat System module fails if the grok expressions cannot be matched to a pattern. Filebeat Syslog dashboard cannot be loaded if the grok expressions cannot be matched to a pattern. Apr 5, 2017
@tsg tsg added the bug label Apr 6, 2017
@tsg
Copy link
Contributor

tsg commented Apr 6, 2017

The Grok error should be fixed by the above PR. I didn't have any other errors when running against your log file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants