On Nov 9, 2015, at 10:48 AM, Stefan Negrea <snegrea@redhat.com> wrote:

Hello,

That document uses what is already implemented as a base. Phase 0 (a prototype phase) should take the current implementation to the next level. All the things in the document where logical increments to what we have today. The goal was to have a quick Phase 0 to build something that we can get feedback on.

As for the requirements, there are no requirement and there will probably be very little requirements. There is no external entity to give us some requirements at this stage. If you consider that what is proposed in the document is wrong, I open to suggestions. However, I caution against inaction or slow action.

Whatever we do should follow two basic principles:
1) Fast phase, 2-3 weeks of development
2) Build something simple that enables more complicated features in the future


More replies inline below ....


Thank you,
Stefan 


----- Original Message -----

From: "Thomas Segismont" <tsegismo@redhat.com>
To: hawkular-dev@lists.jboss.org
Sent: Monday, November 9, 2015 9:16:48 AM
Subject: Re: [Hawkular-dev] Hawkular Metrics + Hawkular Alerts - Phase 0

Hi,

Phase 0 is already implemented:
- Metrics can receive data over HTTP
- Metrics can publish inserted data to the bus
- Webhooks can be created/configured via the Alerts API
- Alerts is able to consume data from the bus

That is not what the document states as goals for Phase 0. As the document is written what you described is a prerequisite for Phase 0.

I can't see why we need to expose an endpoint in Metrics API to setup a
set of conditions in Alerts. The Alerts API does the job.

Disconnected APIs are not an integrated solutions. Just as an example, the are issues with the maturity of the APIs on both ends. Until we go through the exercise of trying to integrate the two in a user facing feature we will not see the differences or be able to provide something meaningful to users.

Do you already know the use cases for Phase 1?

There are no requirements, and probably there will be no requirements in the next month (or even more). That is not the way to approach this.

Regards,
Thomas


Le 06/11/2015 00:01, Stefan Negrea a écrit :

Hello Everybody,

I want to open the discussion around the design and implementation for the
Hawkular Metrics and Hawkular Alerts integration. I created a document
with the scope and objectives for Phase 0. It is called Phase 0 because
this should be a proof of concept of the type of functionality to be
delivered in the future with a scope of getting early feedback on our
ideas. The goal is to deliver this phase in Hawkular Metrics 0.10.0, and
have something implemented in the next 2 weeks.

I've had discussions with developers on both teams and updated the document
based on those discussions. My goal was to first refine the ideas to a
coherent state before publishing a first draft. I am now opening the
document and the discussion to the entire Hawkular community.

The one point where we need additional help is highlighted in red with a
bigger font in the document.

Please feel free to comment in the document, reply to this email, or
contact me (stefan_n) on #hawkular on freenode. If you do not have access
to the document please email me privately and will grant access. Any and
all the feedback is more than welcomed.


Link:
https://docs.google.com/document/d/1PwOGGysO0ppc2VPl80i4ye9pZI-Ugd4gObzQ5GFid4Y


Thank you,
Stefan Negrea

Software Engineer

_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev

_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev

_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev