Seems like the UI discussion has fallen off the inboxes. We should definitely open up a separate Jira and discussion on the best way to process elastic search template management. This feels like a non-UI question to me, since it would apply equally to any other parser config method. I’ll start a separate discuss for that.
In the meantime it would be great to hear more from the community on the UI at http://imgur.com/a/QAQyu? Is there anything you see missing around sensor config here? Does it look useful? Does the flow match the way you would currently think about setting up sensors? It would be great to get some thoughts. Simon > On 1 Feb 2017, at 12:07, Simon Elliston Ball <si...@simonellistonball.com> > wrote: > > The MPack creates elastic templates for the standard parsers included in the > pack. > > However, when creating new sensors we should be able to infer Elastic > templates from the schema. There are certain fields that we need to mark > types for to generate those templates (e.g. date / time fields). This goes > back to the debate we had a while ago about, for example, typing in the grok > parser, but applies for others too. I suspect that since we should be able to > infer all the types needed for templates, this is more an excellent feature > enhancement for the REST api layer, unless anyone can think of a reason we > would need explicit type definition in the > > > >> On 1 Feb 2017, at 19:54, Nick Allen <n...@nickallen.org> wrote: >> >> The Index templates are currently handled in the Ambari MPack (unless you >> are suggesting some additional functionality beyond what the Ambari MPack >> gives us today.) >> >> I think there is always going to be a fuzzy, gray line between what the >> Ambari MPack should do and what the Management UI should do. I think it >> works fine in Ambari today, but I could be convinced otherwise. >> >> >> >> On Wed, Feb 1, 2017 at 9:51 AM, Dima Kovalyov <dima.koval...@sstech.us> >> wrote: >> >>> Thank you Houshang, >>> >>> That looks absolutely great, loved it! >>> Will it make sense to also add ElasticSearch index templates >>> querying/creation here? >>> >>> - Dima >>> >>> On 02/01/2017 02:06 AM, Houshang Livian wrote: >>>> Hello Metron Community, >>>> >>>> We have constructed a Management Module UI, built on top of METRON-503 >>> (REST API) (currently under review). This Module gives users the ability to >>> setup and administer much of the product through the UI. >>>> >>>> Here are some screens to show you what we are thinking. Please take a >>> look: >>>> http://imgur.com/a/QAQyu? >>>> >>>> Does this look like a reasonable place to start? >>>> Is there anything that is an absolute MUST have or MUST NOT have? >>>> >>>> Houshang Livian >>>> Senior User Experience Designer >>>> Hortonworks >>>> >>>> www.hortonworks.com<http://www.hortonworks.com/> >>>> ________________________________ >>>> >>>> Mobile: (831) 521-4176<tel:(831)%20521-4176> >>>> hliv...@hortonworks.com<mailto:hliv...@hortonworks.com> >>>> ________________________________ >>>> >>>> >>> >>> >> >> >> -- >> Nick Allen <n...@nickallen.org> >
