Re: [DISCUSS] Meta alert Elasticsearch new template requirement ramifications

2017-09-29 Thread Rita McKissick
Hi Justin, I am adding the nested “alert" field requirement to the product documentation, and I had a question: * If the user opts to use the default configuration, will they still need to add the nested “alert” field? When I’m finished with the documentation, I’ll send you a link to make

Re: [DISCUSS] Meta alert Elasticsearch new template requirement ramifications

2017-09-29 Thread Justin Leet
I put up a preliminary PR at https://github.com/apache/metron/pull/780. As noted there, this should almost certainly be under a different heading, and possibly a different README, so feel free to chime in on that. Primary goal is to make sure the content makes sense and get adjustments as needed.

Re: [DISCUSS] Meta alert Elasticsearch new template requirement ramifications

2017-09-29 Thread Otto Fowler
We can also consider this when thinking about creating parsers with archetypes that contain ‘default’ elasticsearch templates. On September 29, 2017 at 10:00:03, Justin Leet (justinjl...@gmail.com) wrote: As part of building a backend for meta-alerts (