It's different in that beaver stores the value as an entry in an array, however I think I'll change that because it doesn't make much sense, but I was following the existing add_field functionally. The way it is now, you would have to reference %{[fieldName1][0]} to get the value, instead of just "fieldName1". 

I just tested this change, and it works fine, I'll commit it to my branch shortly. I'll also change the docs to indicate that it is the functional equivalent of the log stash environment filter. 

Sent from my iPhone

> On Nov 7, 2013, at 13:53, Jose Diaz-Gonzalez <notifications@github.com> wrote:
> 
> In docs/user/usage.rst:
> 
> > +            ],
> > +            "cloudCluster" => [
> > +                [0] "always-cms-services-ext-d0prod"
> > +            ],
> > +            "launchConfig" => [
> > +                [0] "always-cms-services-ext-d0prod-20131030104814"
> > +            ]
> > +        },
> > +          "@timestamp" => "2013-11-07T20:38:32.096Z",
> > +        "@source_path" => "/mnt/logs/jetty/access.log",
> > +               "@type" => "cms-serv-ext",
> > +            "@version" => "1",
> > +                "host" => "10.21.56.68:35245",
> > +    }
> > +
> > +This is very similiar to the logstash environment filter.
> How is it different?
> 
> —
> Reply to this email directly or view it on GitHub.