On Tue, Jul 5, 2016 at 4:05 PM, Stefan Negrea <snegrea@redhat.com> wrote:

On Tue, Jul 5, 2016 at 8:03 AM, Thomas Segismont <tsegismo@redhat.com> wrote:

Le 05/07/2016 à 14:59, Heiko W.Rupp a écrit :
>> 2) The Grafana plugin should be moved under Metrics because is for Metrics
>> > and only Metrics.
> If this is true - can we make it work with H-services as well?
>

The Grafana plugin works with all active flavors of Metrics: standalone,
Openshift-Metrics and Hawkular-Services.

I'm not sure what Stefan meant.

The Grafana plugins works with Metrics deployed on all distributions however, the plugin itself can only be used with the Metrics project, there are no projects (such as Alerts, or Inventory) that will ever integrate with it. That is why I think it should be under the Metrics project and not in another place. The integration itself is very specific to just Metrics, not the entire Hawkular Services.

But then it applies to Hawkular services (the most important Hawkular project) and then should really shine there as much as for Metrics.

We really need to think of Hawkular Metrics as a core part of Hawkular Services, not as a side project. 

Same for the documentation, the documentation to use metrics will need to be part of Hawkular Services documentation, not just a mere pointer to Hawkular metrics and let the user deal with the differences.

Thomas

 

_______________________________________________
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