Logstash example config processing order

[ebeahan]

A community user noted that the example Logstash filter configuration won't behave correctly since the mutate plugin will execute mutations in a set order.

One example from example/logstash/2-ecs-conversion.conf:

copy => { '[destport]' => '[destination][port]' }
convert => { '[destination][port]' => 'integer' }

[webmat]

Nah I think the "bug" label is appropriate.

Looks like we can fix this simply by outputting subsequent mutate filters. Perhaps one for copy, one for rename, and finally one for convert.