Re: [Hawkular-dev] Is this an applicable use-case for Hawkular

----- Original Message ----- > From: "Anton Hughes" <ah(a)tradeworks.io&gt; > To: "Discussions around Hawkular development" < hawkular-dev(a)lists.jboss.org&gt; > Sent: Friday, October 30, 2015 2:16:29 PM > Subject: Re: [Hawkular-dev] Is this an applicable use-case for Hawkular > > Coming back to my original question - and based on some further thinking and > reading of the Hawkular website, I have the following thoughts. > > On the Hawkular website, it is written: > > > > For who ? > There are primarly (BTW - this is spelled incorrect) two types of users. > Users who wants a toolkit to do server/ system monitoring in general, for > them we provide a rich REST API to store metrics, trigger alerts and manage > an inventory of resources > Users who want a full-fledge admin console to monitor and manage middleware > servers (Currently, only WildFly is supported) > I've highlighted the general area that I am most interested - and I think > many others would be too. > Please take a quick look at http://martinfowler.com/eaaDev/EventSourcing.html > . Event Sourcing places emphasis on events of interest - in the Shipping > example in this link the interesting events are: > > > * Ship Arrives > * Ship Departs > > To be able store (store metrics?) and react (trigger alert) in this example > would be very beneficial in many situations. > > I hope this helps to illustrates my use-case. > Hi Anton, Thanks for giving feedback and illustrate this interesting use case. We are finishing the Events feature inside the Hawkular Alerts component and I think that it can work for your requeriments. Once development is in a state to be used I will add some examples following your use case (and publish them on the blog). I hope that might helps. Lucas > On 29 October 2015 at 14:34, Jay Shaughnessy < jshaughn(a)redhat.com > wrote: > > > > > Anton, yes, it can be a little confusing. The Hawkular project is an > end-to-end monitoring and management tool focused on Red Hat software. Today > it basically offers a Wildfly agent for discovering and managing app > servers, their hosted apps, and all of the things that make up those apps. > What is can handle grows with every release. Hawkular leverages a bunch of > components to perform that job. There is HK-Inventory to represent a network > of inventories resources (like an app server, a datasource, a jvm, etc), > HK-Metrics as a Cassandra-backed time-series store, HK-Alerts as a > Drools-backed alerting tool, HK-Accounts as a KeyCloak backed > multi-tenant/auth/authz tool, HK-Console for UI, HK-Bus for a comm backbone, > etc.. > > Some of the HK components, namely HK-Metrics and HK-Alerts support standalone > deployment outside of Hawkular. They are named Hawkular-Metrics and > Hawkular-Alerts because they have been developed as part of the Hawkular > project, but they can be used independently. Hope that helps... > > > On 10/29/2015 9:16 AM, Anton Hughes wrote: > > > > > On 29 October 2015 at 14:12, Jay Shaughnessy < jshaughn(a)redhat.com > wrote: > > > Metrics and Alerts can both be used outside of the Hawkular framework so > really you can store any metric you like, or alert on basically any data you > like. As for Events, the next release of Hawkular Alerts (0.6.0) will > include a new Events feature that you may find interesting. Whereas Alerts > are relatively rare, typically involve human interaction, and run through a > simple life-cycle; Events are likely much more numerous, representing any > sort of happening that a client wants to persist. The interesting thing > about Events in HK-Alerts is that they can be inserted directly via API or > can be generated via Trigger, like an Alert. And Events can also be used as > Trigger conditions, to contribute to further Alert or Event generation. > > Thanks Jay - this sounds really cool! > > I have heard a few times now that hawkular components can be used outside of > the hawkular framework. What exactly is the hawkular framework? As an > outsider I am learning about Hawkular and its features. There is good > documentation on the features, but the underlying framework, not so much. > > Also, regarding documentation, I could not find how to store any 'metric' or > data. Specifically, I am looking to store not just a metric but a pojo. > > > > > -- > Anton Hughes > > > > _______________________________________________ > hawkular-dev mailing list hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > -- > Anton Hughes > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev