<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 30, 2016, at 12:00 PM, Jay Shaughnessy <<a href="mailto:jshaughn@redhat.com" class="">jshaughn@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">On 3/30/2016 10:50 AM, John Sanda
wrote:<br class="">
</div>
<blockquote cite="mid:D1E411A9-0E7A-481D-8760-72D7D3132F19@redhat.com" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Mar 30, 2016, at 10:23 AM, Matt Wringe <<a moz-do-not-send="true" href="mailto:mwringe@redhat.com" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:mwringe@redhat.com">mwringe@redhat.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="font-family: Helvetica; font-size:
12px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space: normal; widows:
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;
float: none; display: inline !important;" class="">-----
Original Message -----</span><br style="font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px;" class="">
<blockquote type="cite" style="font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space: normal; widows:
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">From: "Jay Shaughnessy" <<a moz-do-not-send="true" href="mailto:jshaughn@redhat.com" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:jshaughn@redhat.com">jshaughn@redhat.com</a>><br class="">
To:<span class="Apple-converted-space"> </span><a moz-do-not-send="true" href="mailto:hawkular-dev@lists.jboss.org" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br class="">
Sent: Monday, March 28, 2016 10:59:05 AM<br class="">
Subject: Re: [Hawkular-dev] using hawkular wildfly agent
as a custom java agent<br class="">
<br class="">
<br class="">
I think we should limit ourselves to the Wildfly/EAP agent
that we're already<br class="">
working on, as EAP hosted app monitoring/mgmt is our bread
and butter. Past<br class="">
</blockquote>
<br style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px; float:
none; display: inline !important;" class="">Except this
assumption is not necessarily correct. Hawkular, at least
Hawkular-Metrics, is not only being used just for
Wildfly/EAP monitoring.</span><br style="font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px; float:
none; display: inline !important;" class="">We are using
Hawkular-Metrics in OpenShift (</span><a moz-do-not-send="true" href="https://github.com/openshift/origin-metrics" style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></a><a class="moz-txt-link-freetext" href="https://github.com/openshift/origin-metrics">https://github.com/openshift/origin-metrics</a><span style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px; float:
none; display: inline !important;" class="">) and there
are other potential integration points that are being
looking into. If we only want to handle the Wildfly/EAP
case, then we really need to take a good look and
determine if these other integrations make sense or not.
Otherwise we should really start to look beyond just
Wildfly/EAP so that these integration can be handled
better.</span><br style="font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space: normal; widows:
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
</div>
</blockquote>
<div class=""><br class="">
</div>
</div>
We are actively working on other integration efforts, so we
definitely need to look beyond WildFly/EAP.
<br class="">
</blockquote>
<br class="">
What I'm cautioning against is trying to build all feeds ourselves.
In RHQ we used a lot of manpower to build and maintain a lot of
agent plugins. There is goodness in providing interfaces and
infrastructure that make integrating as easy as possible, and then
trying to avoid doing all of the integration work as well. This is
the model that is working for miq. <br class="">
<br class="">
We have two things going on here, one is the team charter to provide
middleware mgmt via manageiq, using hawkular as the provider. We'll
need agents/feeds to hook up to hawkular to report inventory and
metrics which then make their way to miq. We've got the WFly/EAP
agent and that seems like the likely place to invest the most for MW
mgmt. Then we've got H Metrics, which to some degree has a life
of its own. Certainly the integrations with metrics are important
and as I said before, I think we're already doing the right things,
and just like hawkular overall, making integration easy is our
biggest win because it will allow others to build their own feeds.<br class="">
</div>
_______________________________________________<br class="">hawkular-dev mailing list<br class=""><a href="mailto:hawkular-dev@lists.jboss.org" class="">hawkular-dev@lists.jboss.org</a><br class=""><a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br class=""></div></blockquote><br class=""></div><div>I agree that we are doing the right thing by providing APIs to make integration easier; however it common, reoccurring question is about clients that build on top of those APIs. Considering that these questions keep coming up, I think we need to try to provide a better answer beyond simply providing APIs. I do not think this necessarily means we need to invest a lot in building client libraries. There are plenty of client libraries/tools we can look at, and things like ptrans really help with the integration.</div><br class=""></body></html>