[Hawkular-dev] Hawkular Metrics - Roadmap

[Stefan Negrea]

----- Original Message -----
> From: "Peter Palaga" <ppalaga at redhat.com>
> To: hawkular-dev at lists.jboss.org
> Sent: Wednesday, March 16, 2016 4:36:33 AM
> Subject: Re: [Hawkular-dev] Hawkular Metrics - Roadmap
> 
> Hi Stefan,
> 
> > 5) Developer Support
> >    * Provide a Hawkular Metrics distribution with all components needed for
> >    third-party developers to get a developer environment running with
> >    minimal effort
> >    * An easy-to-use and all-inclusive distribution will avoid having
> >    platform developers configure Wildfly server and a Cassandra cluster
> >    just to test or write integration code
> 
> Does this mean that this distro will contain the Embedded Cassandra from
> Hawkular Commons?

That is the goal, to bundle Embedded Cassandra + Metrics Web API + Wildfly 10 into a single deliverable.

> 
> Has anybody already thought of which auth variant will be present there
> in the distro? (a) Accounts (b) none?

The default Hawkular Metrics auth will be used; which means Accounts is not part of it.

> And actually an equivalent question is which metrics war will be used in
> the distro? - (a) hawkular-metrics-component.war or (b)
> hawkular-metric-rest.war?
> 
> I volunteer to prepare the distro.

Thanks for the offer. John Sanda is already working on this. Please reach out to him to see how you can help.

> 
> Thanks,
> 
> Peter
> 
> > 6) Import & Export Data APIs
> >    * The project already provides a growing set of APIs for querying metric
> >    data, but there are scenarios that require bulk data export into
> >    another system for further analysis. And vice-versa, import large
> >    amounts of data from another system for longer term storage and
> >    aggregation by Hawkular Metrics.
> >    * The goal is to provide APIs optimized for bulk importing or exporting
> >    data. Tools need to be both fast and easy to use, with the primary use
> >    case of moving a large amounts data well beyond the capability of
> >    current REST interface (eg. moving 100GB of data).
> >
> > 7) ElasticSearch integration
> >    * An optional integration with Elastic Search for tasks beyond the
> >    capability of Cassandra.
> >    * Basic examples for this are whole tenant searches and aggregation of
> >    text based data, such as tags, events, and even availability.
> >
> >
> > If you have any other suggestion or would like to contribute to the
> > project, please contact me; feedback is more than welcomed.
> >
> >
> > Thank you,
> > Stefan Negrea
> >
> > Software Engineer
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>