-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Modifiers are not honored in patterns
config option
#1436
Comments
nathanielc
changed the title
Modifies are not honored in
Modifiers are not honored in Jul 1, 2016
patterns
config optionpatterns
config option
sparrc
added a commit
that referenced
this issue
Jul 18, 2016
closes #1436 This also fixes the bad behavior of waiting until runtime to return log parsing pattern compile errors when a pattern was simply unfound.
1 task
sparrc
added a commit
that referenced
this issue
Jul 18, 2016
closes #1436 This also fixes the bad behavior of waiting until runtime to return log parsing pattern compile errors when a pattern was simply unfound.
sparrc
added a commit
that referenced
this issue
Jul 18, 2016
closes #1436 This also fixes the bad behavior of waiting until runtime to return log parsing pattern compile errors when a pattern was simply unfound.
sparrc
added a commit
that referenced
this issue
Jul 18, 2016
closes #1436 This also fixes the bad behavior of waiting until runtime to return log parsing pattern compile errors when a pattern was simply unfound. closes #1418 Also protect against user error when the telegraf user does not have permission to open the provided file. We will now error and exit in this case, rather than silently waiting to get permission to open it.
sparrc
added a commit
that referenced
this issue
Jul 18, 2016
closes #1436 This also fixes the bad behavior of waiting until runtime to return log parsing pattern compile errors when a pattern was simply unfound. closes #1418 Also protect against user error when the telegraf user does not have permission to open the provided file. We will now error and exit in this case, rather than silently waiting to get permission to open it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I expected the following
logparser
config to create aport
tag andpackets
,bytes
as integer fields. But instead I got three string fields and no tags:This config on the other hand worked, which uses the
custom_patterns
config option.Either the
patterns
config needs to error if the patterns contain modifiers or they need to work.Version: 1.0.0-beta2
The text was updated successfully, but these errors were encountered: