Hi! Currently there's no really good way of doing this, I'm afraid. One possibility would be to use drools rules, but in the current version it is a little bit awkward working with them because of the need to restart the server each time the rules change.
However, I think this is a generally useful feature, that can apply to many different scenarios depending on what that lookup table is and where it comes from. I'll file a bug report, but in the meantime if this is important for you, you can try to go the drools route. I've created https://github.com/Graylog2/graylog2-server/issues/644 for this. Many thanks for your contribution! Best, Kay On Thursday, July 31, 2014 9:24:27 PM UTC+2, Hakan Uygun wrote: > > Hi, > > We are working on Graylog extractors for some services (Redis, Mongo, > etc), we have submitted our preliminary work to the extractor directory. > We are having a bit of a problem with mapping the severity of the logs > to Graylog. > > For example in Redis logs [1], characters like *, #, . are used to > define severity of the message. What we can do, is to set the severity > to # for example, which doesn't work obviously. What we want to do is to > create some sort of mapping table, where we read # from the original log > and post it as the "warning" severity. > > How can we do that? > > > [1] http://graylog2.org/extractors/53d164f5e4b08b6a5f9f7b57 > > Hakan > -- > Özgür Yazılım A.Ş. ~ # > http://www.ozguryazilim.com.tr > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
