On Thu, Jul 6, 2017 at 3:34 PM, Stefan Negrea <snegrea@redhat.com> wrote:


Thank you,
Stefan Negrea


On Tue, Jul 4, 2017 at 11:55 AM, Edgar Hernández <ehernand@redhat.com> wrote:

On 07/04/2017 02:41 AM, Thomas Heute wrote:
Agreed, Hawkular Services need more love, not to disappear.
It may be renamed to "Hawkular ManageIQ Provider" on the website if that helps with clarity, but shouldn't disappear.

Also there is no quickstart anymore, it's very rough for people.



 What!? This really comes as a surprise for me. All this time my thinking was that "services" was the thing bundling all parts together and, because of the quickstarts, I believed that "services" was the preferred way to get Hawkular. This idea is further supported by exploring the DockerHub, where only images of Hawkular-services are available.

Also, right after "Inventory" got removed, "services" and "alerts" were somewhat redundant for me because "metrics" is included with "alerts" (and "services" also includes both). And, now, starting with "metrics 0.27.0" I can see that metrics also includes alerts. So, the thing looks more redundant now. But with time I learned that "services" provides the operations api, used by ManageIQ. I don't know if there are other features provided by "services". But those extra features are not documented in the website and people new to Hawkular won't realize what's the idea behind "services".

- Edgar.

Hawkular Metrics started bundling Alerting in October of last year and there are no plans to not bundle it.

​I don't want to side track the discussion too much, but if we are going to target kubernetes/openshift as the base platform, then maybe it does make sense to consider changing the deployment. We should probably have separate containers for metrics and for alerts.​

 

We need to make a differentiation between the components (Alerting, Metrics, Trancing) and their integration into other projects. Hawkular Services is a specific integration for ManageIQ. We need to adjust the content around the core components to be able to build a community around the core components. The integrations are just delivery methods for these components. The integration of Hawkular Metrics and Alerting (there is a special bundle for that just like Hawkular Services) in OpenShift Origin has been used a lot more people than Hawkular Services ever was. Yet it is nowhere featured or discussed. We need to refocus the front page on the core components. Hawkular Services or Hawkular Metrics & Alerting OpenShift Origin (or other future integrations) should be mentioned but in another section.
 


_______________________________________________
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