Thanks. So what does that mean in terms of "filters". (And apologies if it should be obvious am new to this).
There are extractors, attached to inputs. And there are filters attached to streams. Does the "filters" in that config then apply to both? Maybe I should be asking the more broad question of where pipelines should fit in for someone just starting, with no legacy streams or rules or anything else. My IMPRESSION was that pipelines were going to replace (or at least could replace) a lot of the logic that might have appeared in stream rules. in particular, if (for example) I wanted a stream of all network device console logins, I might be processing that in the pipeline then doing a route_to_stream to get them there, rather than rules for the stream. So if such decisions are made in pipelines, would one then have no rules for streams? in which case my question about about the "rules" and what things they related to may be moot? On Monday, August 1, 2016 at 3:55:19 PM UTC-4, Jochen Schalanda wrote: > > Hi Linwood, > > you can lookup and change the order of the traditional filters (such as > extractors) and the new message processor pipeline in the web interface on > the System -> Configurations -> Message Processors Configuration page. > > Cheers, > Jochen > > On Monday, 1 August 2016 21:49:08 UTC+2, Linwood Ferguson wrote: >> >> If a pipeline is connected to the default stream, does that mean it runs >> before the extractors? >> >> Have been experimenting, and I do not seem to see (and the simulator does >> not show) fields created in an extractor associated with input source when >> it arrives in the pipeline. >> >> >> >> -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/63a8534c-f24d-4771-821d-d9e86c66f8ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
