Skip to content
This repository has been archived by the owner on Mar 21, 2023. It is now read-only.

error messages on named parameters and unnamed parameters #235

Open
jalogisch opened this issue Jan 4, 2018 · 0 comments
Open

error messages on named parameters and unnamed parameters #235

jalogisch opened this issue Jan 4, 2018 · 0 comments

Comments

@jalogisch
Copy link

Problem description

When you write a rule you could not mix named and unnamed parameters. That would be clear if the error message would indicate that mixing named and unnamed should not be done.

screenshot 2018-01-04 13 34 44

The mixed setup does not work and gives the error,

set_fields(key_value(to_string($message.message)), prefix: "auditd_" );

while naming the parameters work without any problems

set_fields(fields: key_value(to_string($message.message)), prefix: "auditd_" );

Steps to reproduce the problem

  1. Create a Pipeline rule with mixed named and unnamed parameters
    set_fields(key_value(to_string($message.message)), prefix: "auditd_" );

Environment

  • Graylog Version:2.4
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant