You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the discussion on the Vector repo, I would like it if VRL would tag the matching pattern, so that it's possible to, for example, route to different transformers or sinks based on which pattern was matched.
This is particularly relevant when hosting third-party software on Docker, for example, where you get might application logs mixed in with Apache Access & Error logs, and need to use something like Grok to detect the type and send to a different destination, or do post-processing on, for example.
I'm not sure what form this would take. For example, would a configuration like this:
Add the field grok_pattern=%{common_prefix} %{_status} %{_message} to the output, or grok_pattern=0, or would it be better to allow patterns to accept an object of named patterns, like so:
And (assuming VRL supports passing arrays OR objects like that), the output would automatically include `grok_pattern=status_pattern" if it's an object.
The text was updated successfully, but these errors were encountered:
This would be welcome for me as well. I have a usecase where I am parsing sshd logs, but not all messages have anything sensible to capture to classify them, e.g.,
Per the discussion on the Vector repo, I would like it if VRL would tag the matching pattern, so that it's possible to, for example, route to different transformers or sinks based on which pattern was matched.
This is particularly relevant when hosting third-party software on Docker, for example, where you get might application logs mixed in with Apache Access & Error logs, and need to use something like Grok to detect the type and send to a different destination, or do post-processing on, for example.
I'm not sure what form this would take. For example, would a configuration like this:
Add the field
grok_pattern=%{common_prefix} %{_status} %{_message}
to the output, orgrok_pattern=0
, or would it be better to allowpatterns
to accept an object of named patterns, like so:And (assuming VRL supports passing arrays OR objects like that), the output would automatically include `grok_pattern=status_pattern" if it's an object.
The text was updated successfully, but these errors were encountered: