Taurus and Grok use the same hmtengine codebase for running the custom metrics infrastructure. Based on what you describe, Taurus is more suited for your use-case.
On Fri, Jun 12, 2015 at 11:39 AM, Michael Parco < [email protected]> wrote: > Maybe a suggestion towards my use case then: > > Grok seems ideal because I am attempting to do monitoring and anomaly > detection. It's not in the case of AWS metrics, but my infrastructure as > continuously running metrics collection agents that I display with graphite > displays. The big piece is utilizing the htmengine with the data for > forcasting and anomaly detection. I figured it would be easier to integrate > with Grok and just build into it with custom metrics, am I far off with > that though? > > I will certainly look into taurus. Eventually the end goal is to build > from the ground up and customize an application building on top of > htmengine into a custom app, but for test and demo purposes figured I would > utilize existing frameworks > > On Fri, Jun 12, 2015 at 2:31 PM, Matthew Taylor <[email protected]> wrote: > >> On Fri, Jun 12, 2015 at 11:18 AM, Austin Marshall <[email protected]> >> wrote: >> > I believe Matt is working on such a tutorial. >> >> That I am, but I'm not going to be finish it by the time I go on >> vacation Tuesday. It will be 2-3 weeks before I have anything ready to >> publish. :/ >> >> --------- >> Matt Taylor >> OS Community Flag-Bearer >> Numenta >> >> >
