From miburman at redhat.com  Tue Nov  1 03:08:45 2016
From: miburman at redhat.com (Michael Burman)
Date: Tue, 1 Nov 2016 09:08:45 +0200
Subject: [Hawkular-dev] Labeling needs ?
In-Reply-To: <1109667729.11515636.1477951156706.JavaMail.zimbra@redhat.com>
References: <92C3A812-05CA-4C88-80D4-EC9D3AB4ADDE@redhat.com>
	<F96FA2AB-ABA2-44FE-8533-22C2E5BB680F@redhat.com>
	<1109667729.11515636.1477951156706.JavaMail.zimbra@redhat.com>
Message-ID: <9b64b150-9534-30ff-ae88-89c18f8d24f3@redhat.com>

On 10/31/2016 11:59 PM, Matt Wringe wrote:
> hmm, interesting, we can list all the values values of a key, but not 
> get the list of the key itself? 
No one has asked for such feature (or created a ticket) ;)

Very simple to do though:

return (SELECT DISTINCT tenant_id, tname FROM metrics_tags_idx)
.filter(r -> tenantId.equals(row.getString(0))
.map(r -> r.getString(1))
.distinct()
.toList()
.map(HashSet<T>::new); // Technically redundant, distinct uses a Set already

And there you have it. Now go code ;)

> But the more important tag we want to keep track of is labels, and in 
> this case the value is an array of key:value pairs, which doesn't work 
> too nicely. We store this as a comma separated string and its possible 
> to use regex in this case, but it starts to be really messy to write 
> and is prone to errors. Its really not a great solution and looks 
> really bad when people have to write these complex queries which 
> should be really easy. 
For quick fix, we could use a workaround like some applications that 
have had this feature introduced later in the life-cycle: Use some 
non-visible Unicode to separate the labels. Then just recreate them as 
an array when returning the values.

This is simple to do and regexp matching is easy to fix without any user 
visibility (we split the value before doing the matching).
> This feels like an 'event' what could be marked. I don't know if it 
> needs to be applied to a datapoint directly, or stored in a separate 
> list, or if it even needs to be stored in Hawkular Metrics. 

I'd store it separately and then just in the reading phase enrich the 
data with this. Such as event "deployment started", "deployment ended" 
in the strings metrics (or something like it) and then merge that with 
the datapoints fetched.

> The main thing I think is to be able to query the list of events which have occurred over a specific time frame.
And the previous suggestion answers this one.
> OpenShift has a lot of events it can gather, it could be really cool if we could display these events as marks in the graphs. I don't know if we can use Hawkular Metric string metrics to store these, or something in Alerts to do it. Heapster has a component to gather these events for us (https://github.com/kubernetes/heapster/tree/master/events).
I think we discussed this year or so ago, but nothing ever happened to 
it (I think I even asked if I should implement the events part of 
Heapster, but no one needed it at that point).

Actually, I discussed this first time when I sent the original mail to 
Google guys if we can create the integration to Hawkular from Heapster.
> We may want to keep track of historic changes to tags. I know in OpenShift we store values in tags which can change at any point in time but I don't believe we can query what the values was at time X.
This will require some changes to the data storage, the previous 
suggestions do not. This is a snapshot feature, but we don't have that 
in Cassandra (unlike Accumulo has for example).


From hrupp at redhat.com  Tue Nov  1 04:43:20 2016
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Tue, 01 Nov 2016 09:43:20 +0100
Subject: [Hawkular-dev] Labeling needs ?
In-Reply-To: <1109667729.11515636.1477951156706.JavaMail.zimbra@redhat.com>
References: <92C3A812-05CA-4C88-80D4-EC9D3AB4ADDE@redhat.com>
	<F96FA2AB-ABA2-44FE-8533-22C2E5BB680F@redhat.com>
	<1109667729.11515636.1477951156706.JavaMail.zimbra@redhat.com>
Message-ID: <D3AD1164-A4F3-4CED-A9AC-479140B95281@redhat.com>

On 31 Oct 2016, at 22:59, Matt Wringe wrote:
>>     * Post-tagging of data points (tagging could be provoked by 
>> another
>>     system that e.g. parses log files and sees an anomaly) The idea 
>> behind
>>     it is that one should be able to create tags at certain points in 
>> time
>>     for a single metric or a list of metrics to uniquely identify 
>> that point
>>     in time for queries (relative performance of two versions of a
>>     deployment).
>
> This feels like an 'event' what could be marked. I don't know if it 
> needs to be applied to a datapoint directly, or stored in a separate 
> list, or if it even needs to be stored in Hawkular Metrics.

While I formulated it as it has to be on a (set of) datapoints,
this does not imply any technical implementation.
You are absolutely right, that this could be a separate
map < label, < timestamp, set <metrics>>>
to record the time it applies and the affected metrics.

> The main thing I think is to be able to query the list of events which 
> have occurred over a specific time frame.

Exactly. And to be able to get metric data in a from-label
to-label (or 'til-now' or '+8h') way
>
> OpenShift has a lot of events it can gather, it could be really cool 
> if we could display these events as marks in the graphs. I don't know 
> if we can use Hawkular Metric string

+1

> Do individual data points have tags applied to them? Or only the 
> overall metric?

There are tags on the metric definitions, but I would not want
to overload them with those "events".

> We may want to keep track of historic changes to tags. I know in 
> OpenShift we store values in tags which can change at any point in 
> time but I don't believe we can query what the values was at time X.

From miburman at redhat.com  Tue Nov  1 06:03:40 2016
From: miburman at redhat.com (Michael Burman)
Date: Tue, 1 Nov 2016 12:03:40 +0200
Subject: [Hawkular-dev] Labeling needs ?
In-Reply-To: <9b64b150-9534-30ff-ae88-89c18f8d24f3@redhat.com>
References: <92C3A812-05CA-4C88-80D4-EC9D3AB4ADDE@redhat.com>
	<F96FA2AB-ABA2-44FE-8533-22C2E5BB680F@redhat.com>
	<1109667729.11515636.1477951156706.JavaMail.zimbra@redhat.com>
	<9b64b150-9534-30ff-ae88-89c18f8d24f3@redhat.com>
Message-ID: <92b75814-3c96-ff64-5fd9-8cf3889b61e9@redhat.com>

On 11/01/2016 09:08 AM, Michael Burman wrote:
> And there you have it. Now go code ;)
Well, I was nice this time, HWKMETRICS-532 and PR #676. I added 
filtering abilities on top of the requested feature.

   - Micke

From jshaughn at redhat.com  Tue Nov  1 08:23:04 2016
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Tue, 1 Nov 2016 08:23:04 -0400
Subject: [Hawkular-dev] Labeling needs ?
In-Reply-To: <9b64b150-9534-30ff-ae88-89c18f8d24f3@redhat.com>
References: <92C3A812-05CA-4C88-80D4-EC9D3AB4ADDE@redhat.com>
	<F96FA2AB-ABA2-44FE-8533-22C2E5BB680F@redhat.com>
	<1109667729.11515636.1477951156706.JavaMail.zimbra@redhat.com>
	<9b64b150-9534-30ff-ae88-89c18f8d24f3@redhat.com>
Message-ID: <dc50c263-0e3e-57e6-dda8-be96c261bda9@redhat.com>



> OpenShift has a lot of events it can gather, it could be really cool 
> if we could display these events as marks in the graphs. I don't know 
> if we can use Hawkular Metric string metrics to store these, or 
> something in Alerts to do it. Heapster has a component to gather these 
> events for us 
> (https://github.com/kubernetes/heapster/tree/master/events). 

It would seem best to consolidate storage in metrics so that data is all 
available, and possible more able to be correlated, via the same API.  
Havng said that, alerting can store events in its own way. They can be 
tagged (no tag change history).  They can be queried by date range.  
They are partitioned mainly by tenant.  The storage model in alerting 
may not be as scalable as metrics.  Incoming events can optionally be 
diverted into trigger evaluation, and in that way incoming events could 
trigger other events/alerts, or kick off actions.

From mazz at redhat.com  Tue Nov  1 22:29:51 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Tue, 1 Nov 2016 22:29:51 -0400 (EDT)
Subject: [Hawkular-dev] cadvisor metric collector?
In-Reply-To: <1665773475.3152748.1478053781971.JavaMail.zimbra@redhat.com>
Message-ID: <1705692569.3152927.1478053791892.JavaMail.zimbra@redhat.com>

Am I dreaming, or do I remember someone writing a cadvisor client that pulls the cadvisor metrics and stores them to H-Metrics? For some reason, I have it in my head that Thomas S. did something like this already.

From theute at redhat.com  Wed Nov  2 03:12:26 2016
From: theute at redhat.com (Thomas Heute)
Date: Wed, 2 Nov 2016 08:12:26 +0100
Subject: [Hawkular-dev] cadvisor metric collector?
In-Reply-To: <1705692569.3152927.1478053791892.JavaMail.zimbra@redhat.com>
References: <1665773475.3152748.1478053781971.JavaMail.zimbra@redhat.com>
	<1705692569.3152927.1478053791892.JavaMail.zimbra@redhat.com>
Message-ID: <CA+aN=Mr-SNag7LU+ZWO2uLU5-KRUkL2JjM-djwqXKKcWkAvf6Q@mail.gmail.com>

There is Heapster reading from cAdvisor, and then there is the Heapster
sink for Hawkular Metrics, is it what you have in mind ?

On Wed, Nov 2, 2016 at 3:29 AM, John Mazzitelli <mazz at redhat.com> wrote:

> Am I dreaming, or do I remember someone writing a cadvisor client that
> pulls the cadvisor metrics and stores them to H-Metrics? For some reason, I
> have it in my head that Thomas S. did something like this already.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161102/b2e583ce/attachment.html 

From mazz at redhat.com  Wed Nov  2 09:34:26 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Wed, 2 Nov 2016 09:34:26 -0400 (EDT)
Subject: [Hawkular-dev] cadvisor metric collector?
In-Reply-To: <CA+aN=Mr-SNag7LU+ZWO2uLU5-KRUkL2JjM-djwqXKKcWkAvf6Q@mail.gmail.com>
References: <1665773475.3152748.1478053781971.JavaMail.zimbra@redhat.com>
	<1705692569.3152927.1478053791892.JavaMail.zimbra@redhat.com>
	<CA+aN=Mr-SNag7LU+ZWO2uLU5-KRUkL2JjM-djwqXKKcWkAvf6Q@mail.gmail.com>
Message-ID: <958758688.3265143.1478093666252.JavaMail.zimbra@redhat.com>

> There is Heapster reading from cAdvisor, and then there is the Heapster
> sink for Hawkular Metrics, is it what you have in mind ?

For some reason I thought we (Hawkular team) also wrote a cadvisor client, too (that actually makes the HTTP requests to cadvisor and pulls the stats down).

> 
> On Wed, Nov 2, 2016 at 3:29 AM, John Mazzitelli <mazz at redhat.com> wrote:
> 
> > Am I dreaming, or do I remember someone writing a cadvisor client that
> > pulls the cadvisor metrics and stores them to H-Metrics? For some reason, I
> > have it in my head that Thomas S. did something like this already.
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> >
> >
> 

From snegrea at redhat.com  Wed Nov  2 12:32:13 2016
From: snegrea at redhat.com (Stefan Negrea)
Date: Wed, 2 Nov 2016 11:32:13 -0500
Subject: [Hawkular-dev] cadvisor metric collector?
In-Reply-To: <958758688.3265143.1478093666252.JavaMail.zimbra@redhat.com>
References: <1665773475.3152748.1478053781971.JavaMail.zimbra@redhat.com>
	<1705692569.3152927.1478053791892.JavaMail.zimbra@redhat.com>
	<CA+aN=Mr-SNag7LU+ZWO2uLU5-KRUkL2JjM-djwqXKKcWkAvf6Q@mail.gmail.com>
	<958758688.3265143.1478093666252.JavaMail.zimbra@redhat.com>
Message-ID: <CADt-fV-n+UdD393oUfCeaXyhhAQ3ozj6mUrVxZ6=D2c_vxAf4g@mail.gmail.com>

Hello,

There is a  sub-project in Metrics that has external integrations but
cadvisor is not there because the approach for "ptrans" is along the lines
of a proxy to Metrics. Do you think cadvisor can be added there?


Here is the relevant documentation:

https://github.com/hawkular/hawkular-metrics/tree/master/clients/ptranslator


Thank you,
Stefan Negrea


On Wed, Nov 2, 2016 at 8:34 AM, John Mazzitelli <mazz at redhat.com> wrote:

> > There is Heapster reading from cAdvisor, and then there is the Heapster
> > sink for Hawkular Metrics, is it what you have in mind ?
>
> For some reason I thought we (Hawkular team) also wrote a cadvisor client,
> too (that actually makes the HTTP requests to cadvisor and pulls the stats
> down).
>
> >
> > On Wed, Nov 2, 2016 at 3:29 AM, John Mazzitelli <mazz at redhat.com> wrote:
> >
> > > Am I dreaming, or do I remember someone writing a cadvisor client that
> > > pulls the cadvisor metrics and stores them to H-Metrics? For some
> reason, I
> > > have it in my head that Thomas S. did something like this already.
> > > _______________________________________________
> > > hawkular-dev mailing list
> > > hawkular-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> > >
> > >
> > >
> >
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161102/2b0b75be/attachment-0001.html 

From hrupp at redhat.com  Sat Nov  5 05:50:00 2016
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Sat, 05 Nov 2016 10:50:00 +0100
Subject: [Hawkular-dev] Pom updates ..
Message-ID: <64B2C81E-F09C-4A5A-86D5-87F7C704DC9C@redhat.com>

Hey,

parent pom has been updated to v49 and is available on Central

commons pom has been updated to include parent v49 and is now at 0.8.0.Final
for the release and 0.9.0-SNAPSHOT for the main development stream.

The POM-update will need a day to be available from central.

So for artifacts using commons please bump the dependency to 0.8.0.Final

From jmartine at redhat.com  Wed Nov  9 12:50:09 2016
From: jmartine at redhat.com (Josejulio Martinez Magana)
Date: Wed, 9 Nov 2016 11:50:09 -0600
Subject: [Hawkular-dev] JDG and Hawkular
Message-ID: <CAD4MJED+e6wFFin8pjZr-Wu2oZhLMEHzbi_k5fU0vyTB0pxO2g@mail.gmail.com>

Hello,

Thomas asked me to take a look at how JDG 7 (based on EAP 7.0) worked along
with Hawkular and ManageIQ.

I installed the Hawkular wildfly agent (on the JDG) and started it with:

./bin/standalone.sh -Djboss.socket.binding.port-offset=1000

and right after starting, when performing a discovery (i think) it throws
the following exception:

ERROR [org.jboss.as.controller.management-operation] (Hawkular WildFly
Agent Full Discovery Scan-1) WFLYCTL0013: Operation ("read-attribute")
failed - address: ([
    ("socket-binding-group" => "standard-sockets"),
    ("socket-binding" => "http")

Aside from that exception It seems to be working well with
hawkular-services and ManageIQ. I could do deployments, undeploy, create
datasources, stop the server, and so on.

I'm not sure if the discovery process ends unexpectedly with that exception
or if it continues.
Anyone know if this could affect discovery of other resources ?

I attached a minimal server.log of JDG as i didn't see anything relevant on
Hawkular-services console.

Thanks,
  Josejulio.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161109/8e419d42/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: server.log
Type: text/x-log
Size: 20921 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161109/8e419d42/attachment-0001.bin 

From mazz at redhat.com  Wed Nov  9 12:59:16 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Wed, 9 Nov 2016 12:59:16 -0500 (EST)
Subject: [Hawkular-dev] JDG and Hawkular
In-Reply-To: <CAD4MJED+e6wFFin8pjZr-Wu2oZhLMEHzbi_k5fU0vyTB0pxO2g@mail.gmail.com>
References: <CAD4MJED+e6wFFin8pjZr-Wu2oZhLMEHzbi_k5fU0vyTB0pxO2g@mail.gmail.com>
Message-ID: <1056043054.593977.1478714356475.JavaMail.zimbra@redhat.com>

They must not define an http socket binding in the JDG app server's config (look in its standalone.xml and see). If it is true that they simply don't define that, its not a problem, the agent just doesn't collect data for it (I believe this is resource configuration property - it will just not get collected). Error message is just saying it can't find that resource property to collect.

so look in the managed JDG server's standalone.xml's <socket-binding-group> section and I suspect you won't find "http" in the "standard-sockets".

----- Original Message -----
> Hello,
> 
> Thomas asked me to take a look at how JDG 7 (based on EAP 7.0) worked along
> with Hawkular and ManageIQ.
> 
> I installed the Hawkular wildfly agent (on the JDG) and started it with:
> 
> ./bin/standalone.sh -Djboss.socket.binding.port-offset=1000
> 
> and right after starting, when performing a discovery (i think) it throws the
> following exception:
> 
> ERROR [org.jboss.as.controller.management-operation] (Hawkular WildFly Agent
> Full Discovery Scan-1) WFLYCTL0013: Operation ("read-attribute") failed -
> address: ([
> ("socket-binding-group" => "standard-sockets"),
> ("socket-binding" => "http")
> 
> Aside from that exception It seems to be working well with hawkular-services
> and ManageIQ. I could do deployments, undeploy, create datasources, stop the
> server, and so on.
> I'm not sure if the discovery process ends unexpectedly with that exception
> or if it continues.
> Anyone know if this could affect discovery of other resources ?
> 
> I attached a minimal server.log of JDG as i didn't see anything relevant on
> Hawkular-services console.
> 
> Thanks,
> Josejulio.
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From jmartine at redhat.com  Wed Nov  9 13:05:41 2016
From: jmartine at redhat.com (Josejulio Martinez Magana)
Date: Wed, 9 Nov 2016 12:05:41 -0600
Subject: [Hawkular-dev] JDG and Hawkular
In-Reply-To: <1056043054.593977.1478714356475.JavaMail.zimbra@redhat.com>
References: <CAD4MJED+e6wFFin8pjZr-Wu2oZhLMEHzbi_k5fU0vyTB0pxO2g@mail.gmail.com>
	<1056043054.593977.1478714356475.JavaMail.zimbra@redhat.com>
Message-ID: <CAD4MJEALD8HQ_P_doWXcA1BU=eU6_GbrO9ici=uaHh7MG0SmhA@mail.gmail.com>

You are right, an http socket is not defined on the standalone.xml.

Thanks.

On Wed, Nov 9, 2016 at 11:59 AM, John Mazzitelli <mazz at redhat.com> wrote:

> They must not define an http socket binding in the JDG app server's config
> (look in its standalone.xml and see). If it is true that they simply don't
> define that, its not a problem, the agent just doesn't collect data for it
> (I believe this is resource configuration property - it will just not get
> collected). Error message is just saying it can't find that resource
> property to collect.
>
> so look in the managed JDG server's standalone.xml's
> <socket-binding-group> section and I suspect you won't find "http" in the
> "standard-sockets".
>
> ----- Original Message -----
> > Hello,
> >
> > Thomas asked me to take a look at how JDG 7 (based on EAP 7.0) worked
> along
> > with Hawkular and ManageIQ.
> >
> > I installed the Hawkular wildfly agent (on the JDG) and started it with:
> >
> > ./bin/standalone.sh -Djboss.socket.binding.port-offset=1000
> >
> > and right after starting, when performing a discovery (i think) it
> throws the
> > following exception:
> >
> > ERROR [org.jboss.as.controller.management-operation] (Hawkular WildFly
> Agent
> > Full Discovery Scan-1) WFLYCTL0013: Operation ("read-attribute") failed -
> > address: ([
> > ("socket-binding-group" => "standard-sockets"),
> > ("socket-binding" => "http")
> >
> > Aside from that exception It seems to be working well with
> hawkular-services
> > and ManageIQ. I could do deployments, undeploy, create datasources, stop
> the
> > server, and so on.
> > I'm not sure if the discovery process ends unexpectedly with that
> exception
> > or if it continues.
> > Anyone know if this could affect discovery of other resources ?
> >
> > I attached a minimal server.log of JDG as i didn't see anything relevant
> on
> > Hawkular-services console.
> >
> > Thanks,
> > Josejulio.
> >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161109/8d1d1a75/attachment.html 

From mazz at redhat.com  Wed Nov  9 19:45:29 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Wed, 9 Nov 2016 19:45:29 -0500 (EST)
Subject: [Hawkular-dev] hawkular openshift agent
In-Reply-To: <1209784873.637644.1478738374191.JavaMail.zimbra@redhat.com>
Message-ID: <1516077006.637834.1478738729767.JavaMail.zimbra@redhat.com>

I just updated the docs and provided some convenience scripts that should hopefully make it easier to try out the Hawkular OpenShift Agent. I plan on putting together more stuff on this - perhaps a blog or video - but I just wanted to get it out there now in case anyone can try it out and let me know if it works or if there are things that I missed.

See the README:

https://github.com/hawkular/hawkular-openshift-agent/blob/master/README.adoc

The new scripts are here:

https://github.com/hawkular/hawkular-openshift-agent/tree/master/deploy/openshift

The idea is there are now "simple" steps to perform that downloads, builds, and runs an OpenShift environment for you. From there, you run other scripts that deploy the agent in that OpenShift environment. So those docs and those scripts basically take you from nothing to a running OpenShift environment with Hawkular Metrics and the Hawkular OpenShift Agent running inside.

P.S. Special thanks to Matt Wringe, OpenShift whisperer. It would have taken me at least a month to get this far without him walking me through this yesterday :)

From theute at redhat.com  Thu Nov 10 03:44:21 2016
From: theute at redhat.com (Thomas Heute)
Date: Thu, 10 Nov 2016 09:44:21 +0100
Subject: [Hawkular-dev] JDG and Hawkular
In-Reply-To: <CAD4MJEALD8HQ_P_doWXcA1BU=eU6_GbrO9ici=uaHh7MG0SmhA@mail.gmail.com>
References: <CAD4MJED+e6wFFin8pjZr-Wu2oZhLMEHzbi_k5fU0vyTB0pxO2g@mail.gmail.com>
	<1056043054.593977.1478714356475.JavaMail.zimbra@redhat.com>
	<CAD4MJEALD8HQ_P_doWXcA1BU=eU6_GbrO9ici=uaHh7MG0SmhA@mail.gmail.com>
Message-ID: <CA+aN=Mo0o1yea31BbMboj4M_JLoF2q8RgeLjzZ627NMOsn5DcQ@mail.gmail.com>

So do we need to fix the agent or the agent configuration to not spit that
error message ? Or do we need to add the http socket for some reason ?

What do we lose from ManageIQ pov ?

Thomas

On Wed, Nov 9, 2016 at 7:05 PM, Josejulio Martinez Magana <
jmartine at redhat.com> wrote:

> You are right, an http socket is not defined on the standalone.xml.
>
> Thanks.
>
> On Wed, Nov 9, 2016 at 11:59 AM, John Mazzitelli <mazz at redhat.com> wrote:
>
>> They must not define an http socket binding in the JDG app server's
>> config (look in its standalone.xml and see). If it is true that they simply
>> don't define that, its not a problem, the agent just doesn't collect data
>> for it (I believe this is resource configuration property - it will just
>> not get collected). Error message is just saying it can't find that
>> resource property to collect.
>>
>> so look in the managed JDG server's standalone.xml's
>> <socket-binding-group> section and I suspect you won't find "http" in the
>> "standard-sockets".
>>
>> ----- Original Message -----
>> > Hello,
>> >
>> > Thomas asked me to take a look at how JDG 7 (based on EAP 7.0) worked
>> along
>> > with Hawkular and ManageIQ.
>> >
>> > I installed the Hawkular wildfly agent (on the JDG) and started it with:
>> >
>> > ./bin/standalone.sh -Djboss.socket.binding.port-offset=1000
>> >
>> > and right after starting, when performing a discovery (i think) it
>> throws the
>> > following exception:
>> >
>> > ERROR [org.jboss.as.controller.management-operation] (Hawkular WildFly
>> Agent
>> > Full Discovery Scan-1) WFLYCTL0013: Operation ("read-attribute") failed
>> -
>> > address: ([
>> > ("socket-binding-group" => "standard-sockets"),
>> > ("socket-binding" => "http")
>> >
>> > Aside from that exception It seems to be working well with
>> hawkular-services
>> > and ManageIQ. I could do deployments, undeploy, create datasources,
>> stop the
>> > server, and so on.
>> > I'm not sure if the discovery process ends unexpectedly with that
>> exception
>> > or if it continues.
>> > Anyone know if this could affect discovery of other resources ?
>> >
>> > I attached a minimal server.log of JDG as i didn't see anything
>> relevant on
>> > Hawkular-services console.
>> >
>> > Thanks,
>> > Josejulio.
>> >
>> > _______________________________________________
>> > hawkular-dev mailing list
>> > hawkular-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
>> >
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161110/44bea3ca/attachment.html 

From gbrown at redhat.com  Thu Nov 10 04:49:20 2016
From: gbrown at redhat.com (Gary Brown)
Date: Thu, 10 Nov 2016 04:49:20 -0500 (EST)
Subject: [Hawkular-dev] Integrating Hawkular Alerts into APM
In-Reply-To: <1891696344.6887392.1478771302493.JavaMail.zimbra@redhat.com>
Message-ID: <1276777823.6887507.1478771360747.JavaMail.zimbra@redhat.com>

Hi all

For anyone interested in integration of Alerts with Hawkular APM: https://issues.jboss.org/browse/HWKAPM-736

Feel free to watch/comment :)

Regards
Gary

From hrupp at redhat.com  Thu Nov 10 05:51:06 2016
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Thu, 10 Nov 2016 11:51:06 +0100
Subject: [Hawkular-dev] JDG and Hawkular
In-Reply-To: <CA+aN=Mo0o1yea31BbMboj4M_JLoF2q8RgeLjzZ627NMOsn5DcQ@mail.gmail.com>
References: <CAD4MJED+e6wFFin8pjZr-Wu2oZhLMEHzbi_k5fU0vyTB0pxO2g@mail.gmail.com>
	<1056043054.593977.1478714356475.JavaMail.zimbra@redhat.com>
	<CAD4MJEALD8HQ_P_doWXcA1BU=eU6_GbrO9ici=uaHh7MG0SmhA@mail.gmail.com>
	<CA+aN=Mo0o1yea31BbMboj4M_JLoF2q8RgeLjzZ627NMOsn5DcQ@mail.gmail.com>
Message-ID: <22D0B74F-4E81-42B7-BE32-6C2E61A82D47@redhat.com>

On 10 Nov 2016, at 9:44, Thomas Heute wrote:

> So do we need to fix the agent or the agent configuration to not spit 
> that
> error message ? Or do we need to add the http socket for some reason ?

I think this line should be removed from the agent config

         <resource-config-dmr name="Bound Address"
                              path="/socket-binding-group=standard-sockets/socket-binding=http"
                              attribute="bound-address" />

so the the agent does not try to look for it.

BUT it may prevent us reporting the primary IP (can't recall if that is 
needed though) - Mazz?

> What do we lose from ManageIQ pov ?

For EAPs we show the bind-address in the details view - that may get 
lost this way





> Thomas
>
> On Wed, Nov 9, 2016 at 7:05 PM, Josejulio Martinez Magana <
> jmartine at redhat.com> wrote:
>
>> You are right, an http socket is not defined on the standalone.xml.
>>
>> Thanks.
>>
>> On Wed, Nov 9, 2016 at 11:59 AM, John Mazzitelli <mazz at redhat.com> 
>> wrote:
>>
>>> They must not define an http socket binding in the JDG app server's
>>> config (look in its standalone.xml and see). If it is true that they 
>>> simply
>>> don't define that, its not a problem, the agent just doesn't collect 
>>> data
>>> for it (I believe this is resource configuration property - it will 
>>> just
>>> not get collected). Error message is just saying it can't find that
>>> resource property to collect.
>>>
>>> so look in the managed JDG server's standalone.xml's
>>> <socket-binding-group> section and I suspect you won't find "http" 
>>> in the
>>> "standard-sockets".
>>>
>>> ----- Original Message -----
>>>> Hello,
>>>>
>>>> Thomas asked me to take a look at how JDG 7 (based on EAP 7.0) 
>>>> worked
>>> along
>>>> with Hawkular and ManageIQ.
>>>>
>>>> I installed the Hawkular wildfly agent (on the JDG) and started it 
>>>> with:
>>>>
>>>> ./bin/standalone.sh -Djboss.socket.binding.port-offset=1000
>>>>
>>>> and right after starting, when performing a discovery (i think) it
>>> throws the
>>>> following exception:
>>>>
>>>> ERROR [org.jboss.as.controller.management-operation] (Hawkular 
>>>> WildFly
>>> Agent
>>>> Full Discovery Scan-1) WFLYCTL0013: Operation ("read-attribute") 
>>>> failed
>>> -
>>>> address: ([
>>>> ("socket-binding-group" => "standard-sockets"),
>>>> ("socket-binding" => "http")
>>>>
>>>> Aside from that exception It seems to be working well with
>>> hawkular-services
>>>> and ManageIQ. I could do deployments, undeploy, create datasources,
>>> stop the
>>>> server, and so on.
>>>> I'm not sure if the discovery process ends unexpectedly with that
>>> exception
>>>> or if it continues.
>>>> Anyone know if this could affect discovery of other resources ?
>>>>
>>>> I attached a minimal server.log of JDG as i didn't see anything
>>> relevant on
>>>> Hawkular-services console.
>>>>
>>>> Thanks,
>>>> Josejulio.
>>>>
>>>> _______________________________________________
>>>> hawkular-dev mailing list
>>>> hawkular-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>>
>>> _______________________________________________
>>> hawkular-dev mailing list
>>> hawkular-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>
>>
>>
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev


-- 
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht M?nchen HRB 153243
Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, 
Eric Shander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161110/93faeebf/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Bildschirmfoto 2016-11-10 um 11.50.33.png
Type: image/png
Size: 32284 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161110/93faeebf/attachment-0001.png 

From mwringe at redhat.com  Thu Nov 10 09:19:44 2016
From: mwringe at redhat.com (Matt Wringe)
Date: Thu, 10 Nov 2016 09:19:44 -0500 (EST)
Subject: [Hawkular-dev] hawkular openshift agent
In-Reply-To: <1516077006.637834.1478738729767.JavaMail.zimbra@redhat.com>
References: <1516077006.637834.1478738729767.JavaMail.zimbra@redhat.com>
Message-ID: <737908519.14313988.1478787584172.JavaMail.zimbra@redhat.com>

----- Original Message -----
> From: "John Mazzitelli" <mazz at redhat.com>
> To: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
> Sent: Wednesday, 9 November, 2016 7:45:29 PM
> Subject: [Hawkular-dev] hawkular openshift agent
> 
> I just updated the docs and provided some convenience scripts that should
> hopefully make it easier to try out the Hawkular OpenShift Agent. I plan on
> putting together more stuff on this - perhaps a blog or video - but I just
> wanted to get it out there now in case anyone can try it out and let me know
> if it works or if there are things that I missed.
> 
> See the README:
> 
> https://github.com/hawkular/hawkular-openshift-agent/blob/master/README.adoc
> 
> The new scripts are here:
> 
> https://github.com/hawkular/hawkular-openshift-agent/tree/master/deploy/openshift
> 
> The idea is there are now "simple" steps to perform that downloads, builds,
> and runs an OpenShift environment for you. From there, you run other scripts
> that deploy the agent in that OpenShift environment. So those docs and those
> scripts basically take you from nothing to a running OpenShift environment
> with Hawkular Metrics and the Hawkular OpenShift Agent running inside.

If you don't want to build OpenShift from source or hack on it more directly, to get a simple setup going its just 'oc cluster up --metrics'

That will start OpenShift in a docker image with metrics already preconfigured.

After that you would have to run the commands to install and setup the agent.

Once you are done with it, running 'oc cluster down' will remove it for you.

It setups a very simple configuration though, and its not great if you want to be able to do any sort of changes or use it more in an advanced setting. For developing metrics stuff, its not very useful.

> 
> P.S. Special thanks to Matt Wringe, OpenShift whisperer. It would have taken
> me at least a month to get this far without him walking me through this
> yesterday :)
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From tsegismo at redhat.com  Thu Nov 10 11:12:28 2016
From: tsegismo at redhat.com (Thomas Segismont)
Date: Thu, 10 Nov 2016 17:12:28 +0100
Subject: [Hawkular-dev] hawkular openshift agent
In-Reply-To: <737908519.14313988.1478787584172.JavaMail.zimbra@redhat.com>
References: <1516077006.637834.1478738729767.JavaMail.zimbra@redhat.com>
	<737908519.14313988.1478787584172.JavaMail.zimbra@redhat.com>
Message-ID: <CAHnC0xiY9bfip_W4+=dS07_xeYcSVw6rw6ttMyu-WzztJu=GBg@mail.gmail.com>

The installation process described by Joel in his latest blog isn't good?
It uses Minishift IIRC.

2016-11-10 15:19 GMT+01:00 Matt Wringe <mwringe at redhat.com>:

> ----- Original Message -----
> > From: "John Mazzitelli" <mazz at redhat.com>
> > To: "Discussions around Hawkular development" <
> hawkular-dev at lists.jboss.org>
> > Sent: Wednesday, 9 November, 2016 7:45:29 PM
> > Subject: [Hawkular-dev] hawkular openshift agent
> >
> > I just updated the docs and provided some convenience scripts that should
> > hopefully make it easier to try out the Hawkular OpenShift Agent. I plan
> on
> > putting together more stuff on this - perhaps a blog or video - but I
> just
> > wanted to get it out there now in case anyone can try it out and let me
> know
> > if it works or if there are things that I missed.
> >
> > See the README:
> >
> > https://github.com/hawkular/hawkular-openshift-agent/blob/
> master/README.adoc
> >
> > The new scripts are here:
> >
> > https://github.com/hawkular/hawkular-openshift-agent/tree/
> master/deploy/openshift
> >
> > The idea is there are now "simple" steps to perform that downloads,
> builds,
> > and runs an OpenShift environment for you. From there, you run other
> scripts
> > that deploy the agent in that OpenShift environment. So those docs and
> those
> > scripts basically take you from nothing to a running OpenShift
> environment
> > with Hawkular Metrics and the Hawkular OpenShift Agent running inside.
>
> If you don't want to build OpenShift from source or hack on it more
> directly, to get a simple setup going its just 'oc cluster up --metrics'
>
> That will start OpenShift in a docker image with metrics already
> preconfigured.
>
> After that you would have to run the commands to install and setup the
> agent.
>
> Once you are done with it, running 'oc cluster down' will remove it for
> you.
>
> It setups a very simple configuration though, and its not great if you
> want to be able to do any sort of changes or use it more in an advanced
> setting. For developing metrics stuff, its not very useful.
>
> >
> > P.S. Special thanks to Matt Wringe, OpenShift whisperer. It would have
> taken
> > me at least a month to get this far without him walking me through this
> > yesterday :)
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161110/8bd873d0/attachment.html 

From mazz at redhat.com  Thu Nov 10 11:20:15 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Thu, 10 Nov 2016 11:20:15 -0500 (EST)
Subject: [Hawkular-dev] hawkular openshift agent
In-Reply-To: <CAHnC0xiY9bfip_W4+=dS07_xeYcSVw6rw6ttMyu-WzztJu=GBg@mail.gmail.com>
References: <1516077006.637834.1478738729767.JavaMail.zimbra@redhat.com>
	<737908519.14313988.1478787584172.JavaMail.zimbra@redhat.com>
	<CAHnC0xiY9bfip_W4+=dS07_xeYcSVw6rw6ttMyu-WzztJu=GBg@mail.gmail.com>
Message-ID: <1850380768.770803.1478794815445.JavaMail.zimbra@redhat.com>

---- Original Message -----
> The installation process described by Joel in his latest blog isn't good?
> It uses Minishift IIRC.

No idea. I followed directions to build from source - and that's what the scripts do (downloads the source, builds it, configures it, runs it)

I don't know what Joel's latest blog says.

For the record, I was originally using OpenShift running in VirtualBox VM, but was hitting some issues (that probably were my fault) so I switched to doing it this new way. I like the new way better anyway because running in a VM is annoying :)

From jtakvori at redhat.com  Thu Nov 10 12:32:54 2016
From: jtakvori at redhat.com (Joel Takvorian)
Date: Thu, 10 Nov 2016 18:32:54 +0100
Subject: [Hawkular-dev] hawkular openshift agent
In-Reply-To: <1850380768.770803.1478794815445.JavaMail.zimbra@redhat.com>
References: <1516077006.637834.1478738729767.JavaMail.zimbra@redhat.com>
	<737908519.14313988.1478787584172.JavaMail.zimbra@redhat.com>
	<CAHnC0xiY9bfip_W4+=dS07_xeYcSVw6rw6ttMyu-WzztJu=GBg@mail.gmail.com>
	<1850380768.770803.1478794815445.JavaMail.zimbra@redhat.com>
Message-ID: <CAJo5TF=Wv4HbZj2uSakVYhFqgDURXiCHfasP9c7xHOsAmT2i-Q@mail.gmail.com>

I wouldn't say using minishift isn't good - it helped me a lot, compared to
the installation process as described in the Helloworld MSA - but that was
before I heard about "oc cluster up". It looks like it is even easier now.

On Thu, Nov 10, 2016 at 5:20 PM, John Mazzitelli <mazz at redhat.com> wrote:

> ---- Original Message -----
> > The installation process described by Joel in his latest blog isn't good?
> > It uses Minishift IIRC.
>
> No idea. I followed directions to build from source - and that's what the
> scripts do (downloads the source, builds it, configures it, runs it)
>
> I don't know what Joel's latest blog says.
>
> For the record, I was originally using OpenShift running in VirtualBox VM,
> but was hitting some issues (that probably were my fault) so I switched to
> doing it this new way. I like the new way better anyway because running in
> a VM is annoying :)
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161110/d7447ede/attachment.html 

From mazz at redhat.com  Thu Nov 10 12:38:46 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Thu, 10 Nov 2016 12:38:46 -0500 (EST)
Subject: [Hawkular-dev] hawkular openshift agent
In-Reply-To: <CAJo5TF=Wv4HbZj2uSakVYhFqgDURXiCHfasP9c7xHOsAmT2i-Q@mail.gmail.com>
References: <1516077006.637834.1478738729767.JavaMail.zimbra@redhat.com>
	<737908519.14313988.1478787584172.JavaMail.zimbra@redhat.com>
	<CAHnC0xiY9bfip_W4+=dS07_xeYcSVw6rw6ttMyu-WzztJu=GBg@mail.gmail.com>
	<1850380768.770803.1478794815445.JavaMail.zimbra@redhat.com>
	<CAJo5TF=Wv4HbZj2uSakVYhFqgDURXiCHfasP9c7xHOsAmT2i-Q@mail.gmail.com>
Message-ID: <463068992.790813.1478799526211.JavaMail.zimbra@redhat.com>

I'm going to play with "oc cluster up" soon. I'm going to be curious what additional steps I'm still going to need to do (compared to building/running from source).

----- Original Message -----
> I wouldn't say using minishift isn't good - it helped me a lot, compared to
> the installation process as described in the Helloworld MSA - but that was
> before I heard about "oc cluster up". It looks like it is even easier now.
> 
> On Thu, Nov 10, 2016 at 5:20 PM, John Mazzitelli <mazz at redhat.com> wrote:
> 
> > ---- Original Message -----
> > > The installation process described by Joel in his latest blog isn't good?
> > > It uses Minishift IIRC.
> >
> > No idea. I followed directions to build from source - and that's what the
> > scripts do (downloads the source, builds it, configures it, runs it)
> >
> > I don't know what Joel's latest blog says.
> >
> > For the record, I was originally using OpenShift running in VirtualBox VM,
> > but was hitting some issues (that probably were my fault) so I switched to
> > doing it this new way. I like the new way better anyway because running in
> > a VM is annoying :)
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> 

From mazz at redhat.com  Sat Nov 12 21:31:31 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Sat, 12 Nov 2016 21:31:31 -0500 (EST)
Subject: [Hawkular-dev] openshift application metrics example
In-Reply-To: <1566948507.1363180.1479003898231.JavaMail.zimbra@redhat.com>
Message-ID: <1024612061.1364211.1479004291851.JavaMail.zimbra@redhat.com>

I added some more to help people demo or try out Hawkular OpenShift Agent. See:

https://github.com/hawkular/hawkular-openshift-agent/blob/master/README.adoc#try-it

If you are looking at this stuff, try that out and let me know if something is missing.

In short, I put together a simple Jolokia-enabled WildFly server docker image that can be deployed into OpenShift via the "deploy-to-openshift.sh" script. That script also creates an example configmap and pod annotation so the agent will immediately begin collecting metrics (assuming, of course, you have an agent deployed in OpenShift - the README explains how to do that, too).

I'm soon going to be able to write a blog or video demo on this now that I have everything working and I have an example Jolokia endpoint that is emitting metrics.

The only thing really missing is there is no way for us to actually SEE the metrics in OpenShift (since obviously the console doesn't know anything about application metrics yet). But I can use Heiko's HawkFX to show the graphs since HawkFX now is able to log into OpenShift's H-Metrics server, thanks Heiko!

From mazz at redhat.com  Mon Nov 14 16:40:48 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 14 Nov 2016 16:40:48 -0500 (EST)
Subject: [Hawkular-dev] hawkular openshift agent demo
In-Reply-To: <1726346435.2286677.1479159503435.JavaMail.zimbra@redhat.com>
Message-ID: <284380595.2287040.1479159648283.JavaMail.zimbra@redhat.com>

As promised, here's a quick 10-minute demo of the Hawkular OpenShift Agent:

https://www.youtube.com/watch?v=jvOPlz7lzyM

And here's my blog that references it: http://management-platform.blogspot.com/2016/11/hawkular-openshift-agent-first-demo.html

Take a look and see what you think. I tried to make it quick and hoped to get it to 5-minutes in length, but that wasn't happening. 10 minutes was as fast as I could go and at least get the point across.

From hrupp at redhat.com  Tue Nov 15 06:09:41 2016
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Tue, 15 Nov 2016 12:09:41 +0100
Subject: [Hawkular-dev] Hawkular-services 0.21 released
Message-ID: <3770B5AA-C034-4063-884D-95367EF16CB1@redhat.com>

Hey,

we have just released Hawkular-services v 0.21
Changes relative to 0.20 are:

* Agent was bumped to 0.24.2.Final
	- it is less silent when it can't connect to a/the server
	- is now reports properties for jdbc drivers
* Inventory was bumped to 1.1.1
	- Speed improvements for inventory sync when agents connect

Unofficial docker images are available from

https://hub.docker.com/r/pilhuhn/hawkular-services/

and for a wf with embedded and enabled agent:
https://hub.docker.com/r/pilhuhn/hawkfly/
https://hub.docker.com/r/pilhuhn/hawkfly-domain/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161115/b8f6922e/attachment-0001.html 

From ploffay at redhat.com  Tue Nov 15 12:01:43 2016
From: ploffay at redhat.com (Pavol Loffay)
Date: Tue, 15 Nov 2016 18:01:43 +0100
Subject: [Hawkular-dev] Hawkular logos
Message-ID: <CAKLecW8DSnXAnzeZhEqhrL8J6OAyMZ=BoiEvVJgs87hES4Z3=Q@mail.gmail.com>

Hello,

does anybody have the logo in the attachment without white background? Is
there some place where I could find all logos we have?

Regards,
-- 
Pavol Loffay
Cell: +421948286055
Red Hat
Purky?ova 111 TPB-B
612 45 Brno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161115/f63a2c36/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hawkular-white-background.png
Type: image/png
Size: 46579 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161115/f63a2c36/attachment-0001.png 

From jpkroehling at redhat.com  Tue Nov 15 12:29:37 2016
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Tue, 15 Nov 2016 18:29:37 +0100
Subject: [Hawkular-dev] Hawkular logos
In-Reply-To: <CAKLecW8DSnXAnzeZhEqhrL8J6OAyMZ=BoiEvVJgs87hES4Z3=Q@mail.gmail.com>
References: <CAKLecW8DSnXAnzeZhEqhrL8J6OAyMZ=BoiEvVJgs87hES4Z3=Q@mail.gmail.com>
Message-ID: <88ebbce1-9a16-f114-389c-f183cfeab1e9@redhat.com>

This should have everything possible:

http://design.jboss.org/hawkular/index.htm

- Juca.

On 11/15/2016 06:01 PM, Pavol Loffay wrote:
> Hello,
>
> does anybody have the logo in the attachment without white background?
> Is there some place where I could find all logos we have?
>
> Regards,
> --
> Pavol Loffay
> Cell: +421948286055
> Red Hat
> Purky?ova 111 TPB-B
> 612 45 Brno
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>

From ploffay at redhat.com  Wed Nov 16 03:03:39 2016
From: ploffay at redhat.com (Pavol Loffay)
Date: Wed, 16 Nov 2016 09:03:39 +0100
Subject: [Hawkular-dev] Hawkular logos
In-Reply-To: <88ebbce1-9a16-f114-389c-f183cfeab1e9@redhat.com>
References: <CAKLecW8DSnXAnzeZhEqhrL8J6OAyMZ=BoiEvVJgs87hES4Z3=Q@mail.gmail.com>
	<88ebbce1-9a16-f114-389c-f183cfeab1e9@redhat.com>
Message-ID: <CAKLecW91RLyw9n32b+xWJjjVQwAZDdFjpFtguRORcPh3Rja=rg@mail.gmail.com>

Great! Thanks I was looking for this long time.


Pavol

On Tue, Nov 15, 2016 at 6:29 PM, Juraci Paix?o Kr?hling <
jpkroehling at redhat.com> wrote:

> This should have everything possible:
>
> http://design.jboss.org/hawkular/index.htm
>
> - Juca.
>
> On 11/15/2016 06:01 PM, Pavol Loffay wrote:
> > Hello,
> >
> > does anybody have the logo in the attachment without white background?
> > Is there some place where I could find all logos we have?
> >
> > Regards,
> > --
> > Pavol Loffay
> > Cell: +421948286055
> > Red Hat
> > Purky?ova 111 TPB-B
> > 612 45 Brno
> >
> >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>



-- 
Pavol Loffay
Cell: +421948286055
Red Hat
Purky?ova 111 TPB-B
612 45 Brno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161116/af42eb62/attachment.html 

From gbrown at redhat.com  Wed Nov 16 04:30:40 2016
From: gbrown at redhat.com (Gary Brown)
Date: Wed, 16 Nov 2016 04:30:40 -0500 (EST)
Subject: [Hawkular-dev] Hawkular APM 0.12.0.Final Released
In-Reply-To: <612661989.8756262.1479288481762.JavaMail.zimbra@redhat.com>
Message-ID: <250392061.8756694.1479288640504.JavaMail.zimbra@redhat.com>

Hi

We are pleased to announce that version 0.12.0.Final of Hawkular APM has been released.

The main highlights of the release are:

* A JavaScript OpenTracing provider
* An Openshift template for installing Hawkular APM
* A prototype JavaAgent that uses ByteMan rules operating on the Java OpenTracing API


For full details of the release, please see: https://github.com/hawkular/hawkular-apm/releases/tag/0.12.0.Final

Regards
Gary

From ploffay at redhat.com  Wed Nov 16 15:56:24 2016
From: ploffay at redhat.com (Pavol Loffay)
Date: Wed, 16 Nov 2016 21:56:24 +0100
Subject: [Hawkular-dev] Hawkular-APM OpenTracing JavaScript Implementation
Message-ID: <CAKLecW_ySgbRA4AiVr+nfR31rBXdGU6EaG0wh-gxG=tjpjm7Vw@mail.gmail.com>

Hello,

maybe you have already noticed that we have implemented JavaScript
OpenTracing provider.

Here [1] is a blog post demonstrating how it can be used and what features
it has.

[1] Blog post:
http://www.hawkular.org/blog/2016/11/16/hawkular-apm-opentracing-js.html
Github repository:
https://github.com/hawkular/hawkular-apm-opentracing-javascript
NPM: https://www.npmjs.com/package/hawkular-apm-opentracing

Regards,
-- 
Pavol Loffay
Cell: +421948286055
Red Hat
Purky?ova 111 TPB-B
612 45 Brno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161116/74e17578/attachment.html 

From jpkroehling at redhat.com  Fri Nov 18 12:23:54 2016
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Fri, 18 Nov 2016 18:23:54 +0100
Subject: [Hawkular-dev] Hawkular APM template for OpenShift
Message-ID: <01d11c45-06b7-8ad5-d1f0-e4da777794b3@redhat.com>

Team,

We have now an OpenShift template file for Hawkular APM, meaning that 
you can now have an APM server up and running in under 2 minutes.

A first version of the template is available here:
https://git.io/vXdvU

And a short demo of this template + our vertx opentracing example is here:

https://www.youtube.com/watch?v=GwnmX_NkyeA

- Juca.

From jshaughn at redhat.com  Mon Nov 21 08:29:49 2016
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Mon, 21 Nov 2016 08:29:49 -0500
Subject: [Hawkular-dev] Reminder - post changes to WF config on this list
Message-ID: <16830a85-71ed-e825-bccd-c996ac25df03@redhat.com>


Lately we've had a few changes that have resulted in some broken test 
setups.  Specifically, changes to ISPN cache definitions in the WF 
configurations.  This can affect ITests, QE tests, etc, outside of the 
project initiating the change.   Please take it into consideration when 
pushing a change like this;  make sure you let people know it's coming 
and potentially generate PRs for affected builds.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161121/4320e93e/attachment.html 

From mazz at redhat.com  Mon Nov 21 14:57:14 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 21 Nov 2016 14:57:14 -0500 (EST)
Subject: [Hawkular-dev] new hawkular openshift agent demo
In-Reply-To: <726328528.1102565.1479758102458.JavaMail.zimbra@redhat.com>
Message-ID: <1102798072.1102969.1479758234155.JavaMail.zimbra@redhat.com>

Below is a blog that points to the new Hawkular OpenShift Agent demo that illustrates being able to use the agent outside of OpenShift.

The idea is that even though the name is Hawkular "OpenShift" Agent, it can still run outside of OpenShift and collect metrics from any endpoint that is network accessible (whether running inside or outside of OpenShift). Demo shows the agent collecting from both a Prometheus endpoint as well as a Jolokia endpoint.

Blog: http://management-platform.blogspot.com/2016/11/hawkular-openshift-demo-running-outside.html

The video is here: https://www.youtube.com/watch?v=Fj_OriyvMc0

From hrupp at redhat.com  Tue Nov 22 02:13:50 2016
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Tue, 22 Nov 2016 08:13:50 +0100
Subject: [Hawkular-dev] Fwd: [cm-ops] Mock hawkular server
References: <CANKiV5UHUUVwHkwDWz1-0AzR0-DyoeeFc0TSLkKOQ3cpwb0cqA@mail.gmail.com>
Message-ID: <60C289B3-8CC6-44A2-92AD-2665393B8AC8@redhat.com>

This is interesting

Forwarded message:

> From: Yaacov Zamir <yzamir at redhat.com>
> To: Container Management Operations <cm-ops at redhat.com>, Jeffrey 
> Phillips <jephilli at redhat.com>
> Subject: [cm-ops] Mock hawkular server
> Date: Mon, 21 Nov 2016 20:15:22 +0200
>
> A mock Hawkular server, it send random numbers to Hawkular clients.
> https://github.com/yaacov/mohawk
>
> Here is a link to a clip showing the use of the mock server to test 
> the
> ad-hoc graphs page:
> https://www.youtube.com/watch?v=R0ASlTeq7dg&t=1s


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161122/774ee703/attachment.html 

From jtakvori at redhat.com  Tue Nov 22 03:47:22 2016
From: jtakvori at redhat.com (Joel Takvorian)
Date: Tue, 22 Nov 2016 09:47:22 +0100
Subject: [Hawkular-dev] Future change in Inventory REST API - impacted
	clients?
Message-ID: <CAJo5TFnCEomvEjkkTo1wvP+u1FYkamKMgsAG3hB50t1irNjvyw@mail.gmail.com>

Hi,

There is a small upcoming change in the Inventory REST API which consists
in removing a deprecated field, as explained in this JIRA:
https://issues.jboss.org/browse/HWKINVENT-200

Basically, "type" has been replaced with "metricDataType" a while ago and
made deprecated, now it's going to be removed. Probably not for the next
release, but for the one after. Meanwhile I'd like to check any existing
usage. What are the potential usages?

- Ruby client: I've already made changes to it
- Java client: it uses the inventory API code, so it should not require any
change
- Go client: does not use inventory (?)
- Python client: does not use inventory (?)
- I'm now having a look at WF & openshift agents

Do you see anything else?

Joel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161122/2624d4cf/attachment-0001.html 

From lponce at redhat.com  Tue Nov 22 03:49:21 2016
From: lponce at redhat.com (Lucas Ponce)
Date: Tue, 22 Nov 2016 03:49:21 -0500 (EST)
Subject: [Hawkular-dev] Future change in Inventory REST API -
	impacted	clients?
In-Reply-To: <CAJo5TFnCEomvEjkkTo1wvP+u1FYkamKMgsAG3hB50t1irNjvyw@mail.gmail.com>
References: <CAJo5TFnCEomvEjkkTo1wvP+u1FYkamKMgsAG3hB50t1irNjvyw@mail.gmail.com>
Message-ID: <1148485760.1420057.1479804561137.JavaMail.zimbra@redhat.com>

I think that ruby test suite should be enough.

But just in case, before to submit the change it could be good if ManageIQ tests are passing.

Some ManageIQ code use the wrapped json code brought by the ruby client.

I guess that if the middleware_*.spec are passing we are fine.

Lucas

----- Mensaje original -----
> De: "Joel Takvorian" <jtakvori at redhat.com>
> Para: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
> Enviados: Martes, 22 de Noviembre 2016 9:47:22
> Asunto: [Hawkular-dev] Future change in Inventory REST API - impacted	clients?
> 
> Hi,
> 
> There is a small upcoming change in the Inventory REST API which consists in
> removing a deprecated field, as explained in this JIRA:
> https://issues.jboss.org/browse/HWKINVENT-200
> 
> Basically, "type" has been replaced with "metricDataType" a while ago and
> made deprecated, now it's going to be removed. Probably not for the next
> release, but for the one after. Meanwhile I'd like to check any existing
> usage. What are the potential usages?
> 
> - Ruby client: I've already made changes to it
> - Java client: it uses the inventory API code, so it should not require any
> change
> - Go client: does not use inventory (?)
> - Python client: does not use inventory (?)
> - I'm now having a look at WF & openshift agents
> 
> Do you see anything else?
> 
> Joel
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From lponce at redhat.com  Tue Nov 22 03:50:56 2016
From: lponce at redhat.com (Lucas Ponce)
Date: Tue, 22 Nov 2016 03:50:56 -0500 (EST)
Subject: [Hawkular-dev] Future change in Inventory REST API
	-	impacted	clients?
In-Reply-To: <1148485760.1420057.1479804561137.JavaMail.zimbra@redhat.com>
References: <CAJo5TFnCEomvEjkkTo1wvP+u1FYkamKMgsAG3hB50t1irNjvyw@mail.gmail.com>
	<1148485760.1420057.1479804561137.JavaMail.zimbra@redhat.com>
Message-ID: <795766108.1420515.1479804656585.JavaMail.zimbra@redhat.com>

Also, I mean a *live* test from middleware_*.spec to the new changes.

ManageIQ uses recorded cassettes with old versions of Hawkular Services.

Lucas

----- Mensaje original -----
> De: "Lucas Ponce" <lponce at redhat.com>
> Para: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
> Enviados: Martes, 22 de Noviembre 2016 9:49:21
> Asunto: Re: [Hawkular-dev] Future change in Inventory REST API -	impacted	clients?
> 
> I think that ruby test suite should be enough.
> 
> But just in case, before to submit the change it could be good if ManageIQ
> tests are passing.
> 
> Some ManageIQ code use the wrapped json code brought by the ruby client.
> 
> I guess that if the middleware_*.spec are passing we are fine.
> 
> Lucas
> 
> ----- Mensaje original -----
> > De: "Joel Takvorian" <jtakvori at redhat.com>
> > Para: "Discussions around Hawkular development"
> > <hawkular-dev at lists.jboss.org>
> > Enviados: Martes, 22 de Noviembre 2016 9:47:22
> > Asunto: [Hawkular-dev] Future change in Inventory REST API - impacted
> > 	clients?
> > 
> > Hi,
> > 
> > There is a small upcoming change in the Inventory REST API which consists
> > in
> > removing a deprecated field, as explained in this JIRA:
> > https://issues.jboss.org/browse/HWKINVENT-200
> > 
> > Basically, "type" has been replaced with "metricDataType" a while ago and
> > made deprecated, now it's going to be removed. Probably not for the next
> > release, but for the one after. Meanwhile I'd like to check any existing
> > usage. What are the potential usages?
> > 
> > - Ruby client: I've already made changes to it
> > - Java client: it uses the inventory API code, so it should not require any
> > change
> > - Go client: does not use inventory (?)
> > - Python client: does not use inventory (?)
> > - I'm now having a look at WF & openshift agents
> > 
> > Do you see anything else?
> > 
> > Joel
> > 
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> > 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From jtakvori at redhat.com  Tue Nov 22 04:26:59 2016
From: jtakvori at redhat.com (Joel Takvorian)
Date: Tue, 22 Nov 2016 10:26:59 +0100
Subject: [Hawkular-dev] Future change in Inventory REST API - impacted
	clients?
In-Reply-To: <795766108.1420515.1479804656585.JavaMail.zimbra@redhat.com>
References: <CAJo5TFnCEomvEjkkTo1wvP+u1FYkamKMgsAG3hB50t1irNjvyw@mail.gmail.com>
	<1148485760.1420057.1479804561137.JavaMail.zimbra@redhat.com>
	<795766108.1420515.1479804656585.JavaMail.zimbra@redhat.com>
Message-ID: <CAJo5TFk=bxaH_5ruc2nJOajDNY=kqNZeu6d0m7g_=5zWp-d5kg@mail.gmail.com>

Gracias Lucas

I'm going to try testing manageiq's middleware spec... will probably ask
for some help :)

On Tue, Nov 22, 2016 at 9:50 AM, Lucas Ponce <lponce at redhat.com> wrote:

> Also, I mean a *live* test from middleware_*.spec to the new changes.
>
> ManageIQ uses recorded cassettes with old versions of Hawkular Services.
>
> Lucas
>
> ----- Mensaje original -----
> > De: "Lucas Ponce" <lponce at redhat.com>
> > Para: "Discussions around Hawkular development" <
> hawkular-dev at lists.jboss.org>
> > Enviados: Martes, 22 de Noviembre 2016 9:49:21
> > Asunto: Re: [Hawkular-dev] Future change in Inventory REST API -
> impacted        clients?
> >
> > I think that ruby test suite should be enough.
> >
> > But just in case, before to submit the change it could be good if
> ManageIQ
> > tests are passing.
> >
> > Some ManageIQ code use the wrapped json code brought by the ruby client.
> >
> > I guess that if the middleware_*.spec are passing we are fine.
> >
> > Lucas
> >
> > ----- Mensaje original -----
> > > De: "Joel Takvorian" <jtakvori at redhat.com>
> > > Para: "Discussions around Hawkular development"
> > > <hawkular-dev at lists.jboss.org>
> > > Enviados: Martes, 22 de Noviembre 2016 9:47:22
> > > Asunto: [Hawkular-dev] Future change in Inventory REST API - impacted
> > >     clients?
> > >
> > > Hi,
> > >
> > > There is a small upcoming change in the Inventory REST API which
> consists
> > > in
> > > removing a deprecated field, as explained in this JIRA:
> > > https://issues.jboss.org/browse/HWKINVENT-200
> > >
> > > Basically, "type" has been replaced with "metricDataType" a while ago
> and
> > > made deprecated, now it's going to be removed. Probably not for the
> next
> > > release, but for the one after. Meanwhile I'd like to check any
> existing
> > > usage. What are the potential usages?
> > >
> > > - Ruby client: I've already made changes to it
> > > - Java client: it uses the inventory API code, so it should not
> require any
> > > change
> > > - Go client: does not use inventory (?)
> > > - Python client: does not use inventory (?)
> > > - I'm now having a look at WF & openshift agents
> > >
> > > Do you see anything else?
> > >
> > > Joel
> > >
> > > _______________________________________________
> > > hawkular-dev mailing list
> > > hawkular-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> > >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161122/05a7515d/attachment.html 

From jshaughn at redhat.com  Tue Nov 22 08:15:04 2016
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Tue, 22 Nov 2016 08:15:04 -0500
Subject: [Hawkular-dev] Future change in Inventory REST API - impacted
 clients?
In-Reply-To: <CAJo5TFk=bxaH_5ruc2nJOajDNY=kqNZeu6d0m7g_=5zWp-d5kg@mail.gmail.com>
References: <CAJo5TFnCEomvEjkkTo1wvP+u1FYkamKMgsAG3hB50t1irNjvyw@mail.gmail.com>
	<1148485760.1420057.1479804561137.JavaMail.zimbra@redhat.com>
	<795766108.1420515.1479804656585.JavaMail.zimbra@redhat.com>
	<CAJo5TFk=bxaH_5ruc2nJOajDNY=kqNZeu6d0m7g_=5zWp-d5kg@mail.gmail.com>
Message-ID: <8b246d8c-42a9-94ec-2b26-dcc3775c0a04@redhat.com>

Hi Joel,

There are a couple of listeners in the services code that use 
inventory.  I took a look and I think they are OK but you may want to 
make sure this like is OK:

https://github.com/hawkular/hawkular-services/blob/master/hawkular-rest/hawkular-listener/src/main/java/org/hawkular/listener/cache/BackfillCacheManager.java#L397

On 11/22/2016 4:26 AM, Joel Takvorian wrote:
> Gracias Lucas
>
> I'm going to try testing manageiq's middleware spec... will probably 
> ask for some help :)
>
> On Tue, Nov 22, 2016 at 9:50 AM, Lucas Ponce <lponce at redhat.com 
> <mailto:lponce at redhat.com>> wrote:
>
>     Also, I mean a *live* test from middleware_*.spec to the new changes.
>
>     ManageIQ uses recorded cassettes with old versions of Hawkular
>     Services.
>
>     Lucas
>
>     ----- Mensaje original -----
>     > De: "Lucas Ponce" <lponce at redhat.com <mailto:lponce at redhat.com>>
>     > Para: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org
>     <mailto:hawkular-dev at lists.jboss.org>>
>     > Enviados: Martes, 22 de Noviembre 2016 9:49:21
>     > Asunto: Re: [Hawkular-dev] Future change in Inventory REST API
>     -      impacted        clients?
>     >
>     > I think that ruby test suite should be enough.
>     >
>     > But just in case, before to submit the change it could be good
>     if ManageIQ
>     > tests are passing.
>     >
>     > Some ManageIQ code use the wrapped json code brought by the ruby
>     client.
>     >
>     > I guess that if the middleware_*.spec are passing we are fine.
>     >
>     > Lucas
>     >
>     > ----- Mensaje original -----
>     > > De: "Joel Takvorian" <jtakvori at redhat.com
>     <mailto:jtakvori at redhat.com>>
>     > > Para: "Discussions around Hawkular development"
>     > > <hawkular-dev at lists.jboss.org
>     <mailto:hawkular-dev at lists.jboss.org>>
>     > > Enviados: Martes, 22 de Noviembre 2016 9:47:22
>     > > Asunto: [Hawkular-dev] Future change in Inventory REST API -
>     impacted
>     > >     clients?
>     > >
>     > > Hi,
>     > >
>     > > There is a small upcoming change in the Inventory REST API
>     which consists
>     > > in
>     > > removing a deprecated field, as explained in this JIRA:
>     > > https://issues.jboss.org/browse/HWKINVENT-200
>     <https://issues.jboss.org/browse/HWKINVENT-200>
>     > >
>     > > Basically, "type" has been replaced with "metricDataType" a
>     while ago and
>     > > made deprecated, now it's going to be removed. Probably not
>     for the next
>     > > release, but for the one after. Meanwhile I'd like to check
>     any existing
>     > > usage. What are the potential usages?
>     > >
>     > > - Ruby client: I've already made changes to it
>     > > - Java client: it uses the inventory API code, so it should
>     not require any
>     > > change
>     > > - Go client: does not use inventory (?)
>     > > - Python client: does not use inventory (?)
>     > > - I'm now having a look at WF & openshift agents
>     > >
>     > > Do you see anything else?
>     > >
>     > > Joel
>     > >
>     > > _______________________________________________
>     > > hawkular-dev mailing list
>     > > hawkular-dev at lists.jboss.org <mailto:hawkular-dev at lists.jboss.org>
>     > > https://lists.jboss.org/mailman/listinfo/hawkular-dev
>     <https://lists.jboss.org/mailman/listinfo/hawkular-dev>
>     > >
>     > _______________________________________________
>     > hawkular-dev mailing list
>     > hawkular-dev at lists.jboss.org <mailto:hawkular-dev at lists.jboss.org>
>     > https://lists.jboss.org/mailman/listinfo/hawkular-dev
>     <https://lists.jboss.org/mailman/listinfo/hawkular-dev>
>     >
>     _______________________________________________
>     hawkular-dev mailing list
>     hawkular-dev at lists.jboss.org <mailto:hawkular-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/hawkular-dev
>     <https://lists.jboss.org/mailman/listinfo/hawkular-dev>
>
>
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161122/b1b36b61/attachment-0001.html 

From jtakvori at redhat.com  Tue Nov 22 08:47:59 2016
From: jtakvori at redhat.com (Joel Takvorian)
Date: Tue, 22 Nov 2016 14:47:59 +0100
Subject: [Hawkular-dev] Future change in Inventory REST API - impacted
	clients?
In-Reply-To: <8b246d8c-42a9-94ec-2b26-dcc3775c0a04@redhat.com>
References: <CAJo5TFnCEomvEjkkTo1wvP+u1FYkamKMgsAG3hB50t1irNjvyw@mail.gmail.com>
	<1148485760.1420057.1479804561137.JavaMail.zimbra@redhat.com>
	<795766108.1420515.1479804656585.JavaMail.zimbra@redhat.com>
	<CAJo5TFk=bxaH_5ruc2nJOajDNY=kqNZeu6d0m7g_=5zWp-d5kg@mail.gmail.com>
	<8b246d8c-42a9-94ec-2b26-dcc3775c0a04@redhat.com>
Message-ID: <CAJo5TFmJQgMZ-iNoSx0cDYK22=2Sm0XRHWDxGSKSXw0DiSik0Q@mail.gmail.com>

It looks good, too. As long as it's using the java api, it should be fine.

On Tue, Nov 22, 2016 at 2:15 PM, Jay Shaughnessy <jshaughn at redhat.com>
wrote:

> Hi Joel,
>
> There are a couple of listeners in the services code that use inventory.
> I took a look and I think they are OK but you may want to make sure this
> like is OK:
>
> https://github.com/hawkular/hawkular-services/blob/master/
> hawkular-rest/hawkular-listener/src/main/java/org/hawkular/listener/cache/
> BackfillCacheManager.java#L397
>
>
> On 11/22/2016 4:26 AM, Joel Takvorian wrote:
>
> Gracias Lucas
>
> I'm going to try testing manageiq's middleware spec... will probably ask
> for some help :)
>
> On Tue, Nov 22, 2016 at 9:50 AM, Lucas Ponce <lponce at redhat.com> wrote:
>
>> Also, I mean a *live* test from middleware_*.spec to the new changes.
>>
>> ManageIQ uses recorded cassettes with old versions of Hawkular Services.
>>
>> Lucas
>>
>> ----- Mensaje original -----
>> > De: "Lucas Ponce" <lponce at redhat.com>
>> > Para: "Discussions around Hawkular development" <
>> hawkular-dev at lists.jboss.org>
>> > Enviados: Martes, 22 de Noviembre 2016 9:49:21
>> > Asunto: Re: [Hawkular-dev] Future change in Inventory REST API -
>> impacted        clients?
>> >
>> > I think that ruby test suite should be enough.
>> >
>> > But just in case, before to submit the change it could be good if
>> ManageIQ
>> > tests are passing.
>> >
>> > Some ManageIQ code use the wrapped json code brought by the ruby client.
>> >
>> > I guess that if the middleware_*.spec are passing we are fine.
>> >
>> > Lucas
>> >
>> > ----- Mensaje original -----
>> > > De: "Joel Takvorian" <jtakvori at redhat.com>
>> > > Para: "Discussions around Hawkular development"
>> > > <hawkular-dev at lists.jboss.org>
>> > > Enviados: Martes, 22 de Noviembre 2016 9:47:22
>> > > Asunto: [Hawkular-dev] Future change in Inventory REST API - impacted
>> > >     clients?
>> > >
>> > > Hi,
>> > >
>> > > There is a small upcoming change in the Inventory REST API which
>> consists
>> > > in
>> > > removing a deprecated field, as explained in this JIRA:
>> > > https://issues.jboss.org/browse/HWKINVENT-200
>> > >
>> > > Basically, "type" has been replaced with "metricDataType" a while ago
>> and
>> > > made deprecated, now it's going to be removed. Probably not for the
>> next
>> > > release, but for the one after. Meanwhile I'd like to check any
>> existing
>> > > usage. What are the potential usages?
>> > >
>> > > - Ruby client: I've already made changes to it
>> > > - Java client: it uses the inventory API code, so it should not
>> require any
>> > > change
>> > > - Go client: does not use inventory (?)
>> > > - Python client: does not use inventory (?)
>> > > - I'm now having a look at WF & openshift agents
>> > >
>> > > Do you see anything else?
>> > >
>> > > Joel
>> > >
>> > > _______________________________________________
>> > > hawkular-dev mailing list
>> > > hawkular-dev at lists.jboss.org
>> > > https://lists.jboss.org/mailman/listinfo/hawkular-dev
>> > >
>> > _______________________________________________
>> > hawkular-dev mailing list
>> > hawkular-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
>> >
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>
>
>
> _______________________________________________
> hawkular-dev mailing listhawkular-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161122/baf3bc14/attachment.html 

From ppalaga at redhat.com  Thu Nov 24 10:26:45 2016
From: ppalaga at redhat.com (Peter Palaga)
Date: Thu, 24 Nov 2016 16:26:45 +0100
Subject: [Hawkular-dev] Srcdeps - some changes to come
Message-ID: <4ef3c749-a0fe-9296-a36a-3c159f8e22ce@redhat.com>

Hi *,

I was able to invest some time into srcdeps in the recent couple of 
months. Srcdeps is now a bit more powerful - esp. it is able to handle 
all kinds of dependencies incl. parents and BoM imports. The new 
functionality was enabled by using the Maven Core Extensions API instead 
of Maven Plugin API.

Technically, srcdeps now provides its own custom implementation of Maven 
Local Repository [1]. In this way srcdeps is able to intercept every 
single request to the Maven Local Repository and eventually build the 
requested artifact from source and install it locally if necessary.

The convention to declare a source dependencies using 
-SRC-revision-{sha1} suffix stayed unchanged. However, the mapping from 
GAVs to git repositories now lives in .mvn/srcdeps.yaml file rather than 
in pom.xml file.

In the coming weeks, I'll be preparing PRs to migrate from the old 
srcdeps-maven-plugin to the new srcdeps core extension.

I'll also introduce mvnw (a.k.a. Maven Wrapper [2]) so that there is a 
common way for developers, CI and srcdeps to get the same clearly 
defined version of Maven.

Are there any concerns or questions?

[1] https://github.com/srcdeps/srcdeps-maven
[2] https://github.com/takari/maven-wrapper#maven-wrapper

Thanks,

Peter

From jshaughn at redhat.com  Tue Nov 29 08:42:58 2016
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Tue, 29 Nov 2016 08:42:58 -0500
Subject: [Hawkular-dev] Reminder - post changes to WF config on this list
In-Reply-To: <16830a85-71ed-e825-bccd-c996ac25df03@redhat.com>
References: <16830a85-71ed-e825-bccd-c996ac25df03@redhat.com>
Message-ID: <0da41679-01b1-e163-7107-a8d6ef668faf@redhat.com>


Filip, and others, Alerting master (1.4.0-SNAPSHOT) has added a new ISPN 
cache:  hawkular-alerts/globalActions

Please add it to test setups as needed.


On 11/21/2016 8:29 AM, Jay Shaughnessy wrote:
>
> Lately we've had a few changes that have resulted in some broken test 
> setups.  Specifically, changes to ISPN cache definitions in the WF 
> configurations.  This can affect ITests, QE tests, etc, outside of the 
> project initiating the change.   Please take it into consideration 
> when pushing a change like this;  make sure you let people know it's 
> coming and potentially generate PRs for affected builds.
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161129/5ffa1fd1/attachment.html 

From theute at redhat.com  Tue Nov 29 09:03:26 2016
From: theute at redhat.com (Thomas Heute)
Date: Tue, 29 Nov 2016 15:03:26 +0100
Subject: [Hawkular-dev] Hawkular Services as Middleware Manager and Ansible
Message-ID: <CA+aN=MrOd6aYjHc0R9Cwt9yYV5Ay0p6_jfL4co4bCfmrTbb4Rw@mail.gmail.com>

I'd like to resume the discussion as how we will enable the following
features:
   - Start a server/domain
   - Find Wildfly servers and instrument them with the agent
with Ansible in the Middleware Manager ?

I'm questioning the packaging and dependencies, Rubens spent some time a
while back and we need to resume/conclude:
https://github.com/hawkular/hawkular-commons/pull/83/files

If I read fast and correctly it seems that:
   - we have a cyclic dependency(with commons and inventory)
   - the code should not be in common (actually the whole commands-gateway
doesn't belong to commons if we consider that commons was supposed to be
shared among Alert/Metrics/APM/Services)
   - The playbooks are not part of Hawkular-services so they would be added
separately ? Or hawkular-services would be less and less generic / more and
more related to the MW Manager ?
   - The code is currently specific to Wildfly ? (Would not work for Fuse
on Karaf or should be modified ?)

https://github.com/hawkular/hawkular-commons/pull/83/files#diff-dd195df81855017bb54e44d7c140c04fR72

Note: While I am not directly suggesting Hawkular Services to be more
specialized as the middleware manager, it may be something we would want.
Hawkular for Manage IQ (currently hawkular-services) and Hawkular for
Kubernetes/OpenShift (currently HAM), the first should extend the second so
that one could just use the first as MW Manager and solution for OpenShift.
It would simplify development and message.


Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161129/8c931d51/attachment.html 

From theute at redhat.com  Tue Nov 29 09:12:48 2016
From: theute at redhat.com (Thomas Heute)
Date: Tue, 29 Nov 2016 15:12:48 +0100
Subject: [Hawkular-dev] Hawkular Services as Middleware Manager and
	Ansible
In-Reply-To: <CA+aN=MrOd6aYjHc0R9Cwt9yYV5Ay0p6_jfL4co4bCfmrTbb4Rw@mail.gmail.com>
References: <CA+aN=MrOd6aYjHc0R9Cwt9yYV5Ay0p6_jfL4co4bCfmrTbb4Rw@mail.gmail.com>
Message-ID: <CA+aN=MqTu3QqGXaDD55cj9G1wGwFSV=Bavem0ZfjsngtqiQA5w@mail.gmail.com>

On Tue, Nov 29, 2016 at 3:03 PM, Thomas Heute <theute at redhat.com> wrote:

> I'd like to resume the discussion as how we will enable the following
> features:
>    - Start a server/domain
>    - Find Wildfly servers and instrument them with the agent
> with Ansible in the Middleware Manager ?
>
> I'm questioning the packaging and dependencies, Rubens spent some time a
> while back and we need to resume/conclude:
> https://github.com/hawkular/hawkular-commons/pull/83/files
>
> If I read fast and correctly it seems that:
>    - we have a cyclic dependency(with commons and inventory)
>    - the code should not be in common (actually the whole commands-gateway
> doesn't belong to commons if we consider that commons was supposed to be
> shared among Alert/Metrics/APM/Services)
>    - The playbooks are not part of Hawkular-services so they would be
> added separately ? Or hawkular-services would be less and less generic /
> more and more related to the MW Manager ?
>    - The code is currently specific to Wildfly ? (Would not work for Fuse
> on Karaf or should be modified ?)
>            https://github.com/hawkular/hawkular-commons/pull/83/
> files#diff-dd195df81855017bb54e44d7c140c04fR72
>

Well the whole command-gateway depend on WF anyway, so we would need a
twist for Karaf/JMX based products


>
>
> Note: While I am not directly suggesting Hawkular Services to be more
> specialized as the middleware manager, it may be something we would want.
> Hawkular for Manage IQ (currently hawkular-services) and Hawkular for
> Kubernetes/OpenShift (currently HAM), the first should extend the second so
> that one could just use the first as MW Manager and solution for OpenShift.
> It would simplify development and message.
>
>
> Thomas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161129/b3876917/attachment-0001.html 

From lkrejci at redhat.com  Tue Nov 29 10:15:08 2016
From: lkrejci at redhat.com (lkrejci at redhat.com)
Date: Tue, 29 Nov 2016 15:15:08 +0000
Subject: [Hawkular-dev] =?utf-8?q?Pozv=C3=A1nka=3A_Storing_Inventory_data_?=
	=?utf-8?q?in_Cassandra_-_St_2016/11/30_3PM_-_4PM_=28CET=29_=28hawk?=
	=?utf-8?q?ular-dev=40lists=2Ejboss=2Eorg=29?=
Message-ID: <001a114024f6c25fb20542720d03@google.com>

Byli jste pozv?ni na n?sleduj?c? ud?lost.

N?zev: Storing Inventory data in Cassandra
Currently, we're storing inventory data in an SQL database. Metrics on the  
other hand store the data in Cassandra. We're exploring how to unify the  
storage backends for Hawkular components and hence the title.

We'll use  
https://docs.google.com/document/d/1Lgv8WE1j0r7rir5hTpV-xutKFChyoNPEH3XSz020ayk  
as a starting point for the discussion.

To join the Meeting:
https://bluejeans.com/8169978803

To join via Browser:
https://bluejeans.com/8169978803/browser

To join with Lync:
https://bluejeans.com/8169978803/lync

To join via Room System:
Video Conferencing System: bjn.vc -or-199.48.152.152
Meeting ID : 8169978803

To join via phone :
1)  Dial:
	+44 203 574 6870
	(see all numbers -  
https://www.intercallonline.com/listNumbersByCode.action?confCode=8169978803)
2)  Enter Conference ID : 8169978803
Kdy: St 2016/11/30 3PM ? 4PM St?edoevropsk? ?as ? Praha
Kde: https://bluejeans.com/8169978803
Kalend??: hawkular-dev at lists.jboss.org
Kdo:
     * lkrejci at redhat.com? autor
     * jsanda at redhat.com
     * jtakvori at redhat.com
     * hawkular-dev at lists.jboss.org

Podrobnosti o ud?losti:  
https://www.google.com/calendar/event?action=VIEW&eid=N28ycmpjMnExMTZjYWJ2NmgxZmNtdmNnbmMgaGF3a3VsYXItZGV2QGxpc3RzLmpib3NzLm9yZw&tok=NjMjcmVkaGF0LmNvbV9mbWlnMm9zdTY5a21hNDdqcmRjMnZlbjRtb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29tYTUwNDYzNzRmNzI5YjRkZWEwZGNlNWE0ODcyNWMwY2UzOGQ4ODU1Yg&ctz=Europe/Prague&hl=cs

Pozv?nka z Kalend??e Google: https://www.google.com/calendar/

Tento e-mail na ??et hawkular-dev at lists.jboss.org jste obdr?eli z toho  
d?vodu, ?e jste ??astn?kem t?to ud?losti.

Chcete-li se odhl?sit z odb?ru ozn?men? o t?to ud?losti, odm?tn?te ud?lost.  
P??padn? si m??ete na adrese https://www.google.com/calendar/ zaregistrovat  
??et Google a ??dit nastaven? ozn?men? pro cel? sv?j kalend??.

P?eposl?n?m t?to pozv?nky byste mohli komukoli z p??jemc? umo?nit, aby  
zm?nil va?i odpov?? na toto pozv?n?. Dal?? informace najdete na  
https://support.google.com/calendar/answer/37135#forwarding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161129/1958b39f/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2204 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161129/1958b39f/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2247 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161129/1958b39f/attachment-0001.bin 

From yvedpath at redhat.com  Tue Nov 29 10:42:08 2016
From: yvedpath at redhat.com (Yogesh Vedpathak)
Date: Tue, 29 Nov 2016 21:12:08 +0530
Subject: [Hawkular-dev] Hawkular
Message-ID: <CAJKedabHg_Pr-SzJkNCp_o5yB8cmsUdJeOiX=zv+Wfd-SpRR6w@mail.gmail.com>

Hi,

As per installation guide of Hawkular, we need to install CCM first. I have
python installed on my RHEL machine. But I am not able to install CCM. Can
someone give suggestions for installing CCM?

Regards,
Yogesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161129/744953ed/attachment.html 

From jsanda at redhat.com  Tue Nov 29 11:30:41 2016
From: jsanda at redhat.com (John Sanda)
Date: Tue, 29 Nov 2016 11:30:41 -0500
Subject: [Hawkular-dev] Hawkular
In-Reply-To: <CAJKedabHg_Pr-SzJkNCp_o5yB8cmsUdJeOiX=zv+Wfd-SpRR6w@mail.gmail.com>
References: <CAJKedabHg_Pr-SzJkNCp_o5yB8cmsUdJeOiX=zv+Wfd-SpRR6w@mail.gmail.com>
Message-ID: <B0869741-4BF2-4FBB-A9CD-63AD7B8E33FC@redhat.com>

Install pip and then `pip install ccm`

> On Nov 29, 2016, at 10:42 AM, Yogesh Vedpathak <yvedpath at redhat.com> wrote:
> 
> Hi,
> 
> As per installation guide of Hawkular, we need to install CCM first. I have python installed on my RHEL machine. But I am not able to install CCM. Can someone give suggestions for installing CCM? 
> 
> Regards,
> Yogesh
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev



From ppalaga at redhat.com  Tue Nov 29 12:06:40 2016
From: ppalaga at redhat.com (Peter Palaga)
Date: Tue, 29 Nov 2016 18:06:40 +0100
Subject: [Hawkular-dev] Srcdeps - some changes to come
In-Reply-To: <4ef3c749-a0fe-9296-a36a-3c159f8e22ce@redhat.com>
References: <4ef3c749-a0fe-9296-a36a-3c159f8e22ce@redhat.com>
Message-ID: <23401600-cfdc-98c0-5fa5-7ad2f50e5b2d@redhat.com>

Hi *,

I have sent a couple of PRs, some of them were merged already. Please go 
through the list and let me know if you see a hawkular project missing 
there?

https://github.com/hawkular/hawkular-parent-pom/pull/93 merged, 
hawkular-parent 50 released

https://github.com/hawkular/hawkular-commons/pull/92 merged

https://github.com/hawkular/hawkular-inventory/pull/319 merged

https://github.com/hawkular/hawkular-apm/pull/694

https://github.com/hawkular/hawkular-metrics/pull/704

https://github.com/hawkular/hawkular-agent/pull/273

https://github.com/hawkular/hawkular-services/pull/104

Thanks,

Peter


On 2016-11-24 16:26, Peter Palaga wrote:
> Hi *,
>
> I was able to invest some time into srcdeps in the recent couple of
> months. Srcdeps is now a bit more powerful - esp. it is able to handle
> all kinds of dependencies incl. parents and BoM imports. The new
> functionality was enabled by using the Maven Core Extensions API instead
> of Maven Plugin API.
>
> Technically, srcdeps now provides its own custom implementation of Maven
> Local Repository [1]. In this way srcdeps is able to intercept every
> single request to the Maven Local Repository and eventually build the
> requested artifact from source and install it locally if necessary.
>
> The convention to declare a source dependencies using
> -SRC-revision-{sha1} suffix stayed unchanged. However, the mapping from
> GAVs to git repositories now lives in .mvn/srcdeps.yaml file rather than
> in pom.xml file.
>
> In the coming weeks, I'll be preparing PRs to migrate from the old
> srcdeps-maven-plugin to the new srcdeps core extension.
>
> I'll also introduce mvnw (a.k.a. Maven Wrapper [2]) so that there is a
> common way for developers, CI and srcdeps to get the same clearly
> defined version of Maven.
>
> Are there any concerns or questions?
>
> [1] https://github.com/srcdeps/srcdeps-maven
> [2] https://github.com/takari/maven-wrapper#maven-wrapper
>
> Thanks,
>
> Peter
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>


From mazz at redhat.com  Tue Nov 29 18:14:26 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Tue, 29 Nov 2016 18:14:26 -0500 (EST)
Subject: [Hawkular-dev] hawkular wildfly agent - jmx - remote and local
In-Reply-To: <2107139364.395107.1480461082397.JavaMail.zimbra@redhat.com>
Message-ID: <1634764273.395255.1480461266596.JavaMail.zimbra@redhat.com>

The Fuse folks asked that we return back the Jolokia/JMX support. So that is now in a PR, waiting for final approval before merging:

https://issues.jboss.org/browse/HWKAGENT-151
https://github.com/hawkular/hawkular-agent/pull/274

In addition, to avoid going over the network to perform Jolokia REST calls when the agent and the managed MBeans are in the same VM, I've added a new local-jmx managed server. So you can define a local-jmx managed server (and still use the same metric-jmx and avail-jmx sets you've defined before for the jolokia support) and have inventory and metrics collected for that stuff, but it goes over the internal MBeanServerConnection rather than a remote Jolokia endpoint. Note that obviously this is only useful if the agent is deployed in the same WildFly as where your MBeans are. But the point is, you define your JMX resources, avails, and metrics just like before - nothign changed there - but instead of using remote-jmx you use local-jmx in <managed-servers>

See:

https://issues.jboss.org/browse/HWKAGENT-152
https://github.com/hawkular/hawkular-agent/pull/275

From theute at redhat.com  Wed Nov 30 01:16:35 2016
From: theute at redhat.com (Thomas Heute)
Date: Wed, 30 Nov 2016 07:16:35 +0100
Subject: [Hawkular-dev] hawkular wildfly agent - jmx - remote and local
In-Reply-To: <1634764273.395255.1480461266596.JavaMail.zimbra@redhat.com>
References: <2107139364.395107.1480461082397.JavaMail.zimbra@redhat.com>
	<1634764273.395255.1480461266596.JavaMail.zimbra@redhat.com>
Message-ID: <CA+aN=MrwGaJWXHaLSUvUzE43BwofmSyHLMvOTkRJRvaJzpbjWQ@mail.gmail.com>

In which case for Fuse it would *not* be on the same JVM ? Is Jolokia part
of Fuse or how would one "set it up" ?

On Wed, Nov 30, 2016 at 12:14 AM, John Mazzitelli <mazz at redhat.com> wrote:

> The Fuse folks asked that we return back the Jolokia/JMX support. So that
> is now in a PR, waiting for final approval before merging:
>
> https://issues.jboss.org/browse/HWKAGENT-151
> https://github.com/hawkular/hawkular-agent/pull/274
>
> In addition, to avoid going over the network to perform Jolokia REST calls
> when the agent and the managed MBeans are in the same VM, I've added a new
> local-jmx managed server. So you can define a local-jmx managed server (and
> still use the same metric-jmx and avail-jmx sets you've defined before for
> the jolokia support) and have inventory and metrics collected for that
> stuff, but it goes over the internal MBeanServerConnection rather than a
> remote Jolokia endpoint. Note that obviously this is only useful if the
> agent is deployed in the same WildFly as where your MBeans are. But the
> point is, you define your JMX resources, avails, and metrics just like
> before - nothign changed there - but instead of using remote-jmx you use
> local-jmx in <managed-servers>
>
> See:
>
> https://issues.jboss.org/browse/HWKAGENT-152
> https://github.com/hawkular/hawkular-agent/pull/275
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161130/a4f9307a/attachment.html 

From tcunning at redhat.com  Wed Nov 30 01:48:17 2016
From: tcunning at redhat.com (Thomas Cunningham)
Date: Wed, 30 Nov 2016 01:48:17 -0500
Subject: [Hawkular-dev] hawkular wildfly agent - jmx - remote and local
In-Reply-To: <CA+aN=MrwGaJWXHaLSUvUzE43BwofmSyHLMvOTkRJRvaJzpbjWQ@mail.gmail.com>
References: <2107139364.395107.1480461082397.JavaMail.zimbra@redhat.com>
	<1634764273.395255.1480461266596.JavaMail.zimbra@redhat.com>
	<CA+aN=MrwGaJWXHaLSUvUzE43BwofmSyHLMvOTkRJRvaJzpbjWQ@mail.gmail.com>
Message-ID: <CALAW+W+ku5fAk4haqSK4SEdJAK4_TfsrM1xH6Md13uxYk1SHHg@mail.gmail.com>

Jolokia is shipped as part of Fuse on both EAP and Karaf.

If it's possible, it'd be nice to have both options.    I think the default
we'd want might be local, but I think there might be use cases where
Jolokia would be preferable (customer doesn't want to run the agent on
every instance, customer is using the ACLs in Fuse to secure MBeans through
jolokia, agent fails to run for some reason).





On Wed, Nov 30, 2016 at 1:16 AM, Thomas Heute <theute at redhat.com> wrote:

> In which case for Fuse it would *not* be on the same JVM ? Is Jolokia part
> of Fuse or how would one "set it up" ?
>
> On Wed, Nov 30, 2016 at 12:14 AM, John Mazzitelli <mazz at redhat.com> wrote:
>
>> The Fuse folks asked that we return back the Jolokia/JMX support. So that
>> is now in a PR, waiting for final approval before merging:
>>
>> https://issues.jboss.org/browse/HWKAGENT-151
>> https://github.com/hawkular/hawkular-agent/pull/274
>>
>> In addition, to avoid going over the network to perform Jolokia REST
>> calls when the agent and the managed MBeans are in the same VM, I've added
>> a new local-jmx managed server. So you can define a local-jmx managed
>> server (and still use the same metric-jmx and avail-jmx sets you've defined
>> before for the jolokia support) and have inventory and metrics collected
>> for that stuff, but it goes over the internal MBeanServerConnection rather
>> than a remote Jolokia endpoint. Note that obviously this is only useful if
>> the agent is deployed in the same WildFly as where your MBeans are. But the
>> point is, you define your JMX resources, avails, and metrics just like
>> before - nothign changed there - but instead of using remote-jmx you use
>> local-jmx in <managed-servers>
>>
>> See:
>>
>> https://issues.jboss.org/browse/HWKAGENT-152
>> https://github.com/hawkular/hawkular-agent/pull/275
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>>
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161130/7e0c7a70/attachment.html 

From theute at redhat.com  Wed Nov 30 03:02:45 2016
From: theute at redhat.com (Thomas Heute)
Date: Wed, 30 Nov 2016 09:02:45 +0100
Subject: [Hawkular-dev] hawkular wildfly agent - jmx - remote and local
In-Reply-To: <CALAW+W+ku5fAk4haqSK4SEdJAK4_TfsrM1xH6Md13uxYk1SHHg@mail.gmail.com>
References: <2107139364.395107.1480461082397.JavaMail.zimbra@redhat.com>
	<1634764273.395255.1480461266596.JavaMail.zimbra@redhat.com>
	<CA+aN=MrwGaJWXHaLSUvUzE43BwofmSyHLMvOTkRJRvaJzpbjWQ@mail.gmail.com>
	<CALAW+W+ku5fAk4haqSK4SEdJAK4_TfsrM1xH6Md13uxYk1SHHg@mail.gmail.com>
Message-ID: <CA+aN=MpwnjSVif+=H1qaBSJusWNrX4xNacpsSAwxDT1yBmvYqw@mail.gmail.com>

ok, thanks

On Wed, Nov 30, 2016 at 7:48 AM, Thomas Cunningham <tcunning at redhat.com>
wrote:

>
> Jolokia is shipped as part of Fuse on both EAP and Karaf.
>
> If it's possible, it'd be nice to have both options.    I think the
> default we'd want might be local, but I think there might be use cases
> where Jolokia would be preferable (customer doesn't want to run the agent
> on every instance, customer is using the ACLs in Fuse to secure MBeans
> through jolokia, agent fails to run for some reason).
>
>
>
>
>
> On Wed, Nov 30, 2016 at 1:16 AM, Thomas Heute <theute at redhat.com> wrote:
>
>> In which case for Fuse it would *not* be on the same JVM ? Is Jolokia
>> part of Fuse or how would one "set it up" ?
>>
>> On Wed, Nov 30, 2016 at 12:14 AM, John Mazzitelli <mazz at redhat.com>
>> wrote:
>>
>>> The Fuse folks asked that we return back the Jolokia/JMX support. So
>>> that is now in a PR, waiting for final approval before merging:
>>>
>>> https://issues.jboss.org/browse/HWKAGENT-151
>>> https://github.com/hawkular/hawkular-agent/pull/274
>>>
>>> In addition, to avoid going over the network to perform Jolokia REST
>>> calls when the agent and the managed MBeans are in the same VM, I've added
>>> a new local-jmx managed server. So you can define a local-jmx managed
>>> server (and still use the same metric-jmx and avail-jmx sets you've defined
>>> before for the jolokia support) and have inventory and metrics collected
>>> for that stuff, but it goes over the internal MBeanServerConnection rather
>>> than a remote Jolokia endpoint. Note that obviously this is only useful if
>>> the agent is deployed in the same WildFly as where your MBeans are. But the
>>> point is, you define your JMX resources, avails, and metrics just like
>>> before - nothign changed there - but instead of using remote-jmx you use
>>> local-jmx in <managed-servers>
>>>
>>> See:
>>>
>>> https://issues.jboss.org/browse/HWKAGENT-152
>>> https://github.com/hawkular/hawkular-agent/pull/275
>>> _______________________________________________
>>> hawkular-dev mailing list
>>> hawkular-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>
>>>
>>>
>>
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161130/48c02175/attachment-0001.html 

From theute at redhat.com  Wed Nov 30 07:08:05 2016
From: theute at redhat.com (theute at redhat.com)
Date: Wed, 30 Nov 2016 12:08:05 +0000
Subject: [Hawkular-dev] [Update] Storing Inventory data in Cassandra
Message-ID: <94eb2c193eacb45c0b0542838ea6@google.com>

I can't join today, Heiko neither.
Feel free to go ahead with the call though and please send a feedback on  
hawkular-dev.

You have been invited to the following event.

Title: Storing Inventory data in Cassandra
Currently, we're storing inventory data in an SQL database. Metrics on the  
other hand store the data in Cassandra. We're exploring how to unify the  
storage backends for Hawkular components and hence the title.

We'll use  
https://docs.google.com/document/d/1Lgv8WE1j0r7rir5hTpV-xutKFChyoNPEH3XSz020ayk  
as a starting point for the discussion.

To join the Meeting:
https://bluejeans.com/8169978803

To join via Browser:
https://bluejeans.com/8169978803/browser

To join with Lync:
https://bluejeans.com/8169978803/lync

To join via Room System:
Video Conferencing System: bjn.vc -or-199.48.152.152
Meeting ID : 8169978803

To join via phone :
1)  Dial:
	+44 203 574 6870
	(see all numbers -  
https://www.intercallonline.com/listNumbersByCode.action?confCode=8169978803)
2)  Enter Conference ID : 8169978803
When: Wed Nov 30, 2016 3pm ? 4pm Zurich
Where: https://bluejeans.com/8169978803
Who:
     * lkrejci at redhat.com - creator
     * jsanda at redhat.com
     * jtakvori at redhat.com
     * hawkular-dev at lists.jboss.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161130/9f990558/attachment.html 

From jshaughn at redhat.com  Wed Nov 30 11:07:20 2016
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Wed, 30 Nov 2016 11:07:20 -0500
Subject: [Hawkular-dev] Hawkular Alerting 1.4.0.Final has been released!
Message-ID: <a0538a2e-789b-984e-d329-f4c10f27c7a9@redhat.com>


The Hawkular Alerting team is happy to announce the release of Hawkular 
Alerting 1.4.0.Final. This
is a feature and fix release with a focus on end-to-end performance 
enhancements.


    Enhancement

  * [HWKALERTS-182 <https://issues.jboss.org/browse/HWKALERTS-182>] -
    Update swagger doc for data types
      o Big improvements to REST API documentation of hawkular.org
  * [HWKALERTS-185 <https://issues.jboss.org/browse/HWKALERTS-185>] -
    Extend perf scenarios for triggers with multiple conditions
  * [HWKALERTS-188 <https://issues.jboss.org/browse/HWKALERTS-188>] -
    Enable a cross-tenant operation for fetching alerts
      o Introducing new /admin query abilities
  * [HWKALERTS-189 <https://issues.jboss.org/browse/HWKALERTS-189>] -
    Add specific examples for import/export and group triggers
  * [HWKALERTS-195 <https://issues.jboss.org/browse/HWKALERTS-195>] -
    import/batch definition changes should defer notifications to the end
  * [HWKALERTS-196 <https://issues.jboss.org/browse/HWKALERTS-196>] -
    Add specific perf examples for large import # of triggers.
  * [HWKALERTS-197 <https://issues.jboss.org/browse/HWKALERTS-197>] -
    Allow different property defaults for different distributions
  * [HWKALERTS-199 <https://issues.jboss.org/browse/HWKALERTS-199>] -
    Improve CacheManager updates
  * [HWKALERTS-201 <https://issues.jboss.org/browse/HWKALERTS-201>] -
    Performance improvement for GetAlerts/Events
  * [HWKALERTS-202 <https://issues.jboss.org/browse/HWKALERTS-202>] -
    Use cassandra batching in alerting backend
  * [HWKALERTS-205 <https://issues.jboss.org/browse/HWKALERTS-205>] -
    Unify properties for email plugin
  * [HWKALERTS-206 <https://issues.jboss.org/browse/HWKALERTS-206>] -
    Improve global plugins
      o Introducing globalActions that can execute on all triggers


    Bug

  * [HWKALERTS-184 <https://issues.jboss.org/browse/HWKALERTS-184>] -
    Response of PUT /{events/}DELETE is no valid JSON
  * [HWKALERTS-187 <https://issues.jboss.org/browse/HWKALERTS-187>] -
    Travis is not updated of new layout and fails searching adoc file
  * [HWKALERTS-200 <https://issues.jboss.org/browse/HWKALERTS-200>] -
    Creation of thousands of triggers takes many hours
      o Huge improvements in CRUD times (down to ~14 minutes in this
        scenario)
  * [HWKALERTS-203 <https://issues.jboss.org/browse/HWKALERTS-203>] -
    Fix issue in Event.compareTo
  * [HWKALERTS-204 <https://issues.jboss.org/browse/HWKALERTS-204>] -
    DataId not published correctly




Hawkular Alerting 1.4.0.Final is available:

  * Immediately a standalone distribution
  * Soon as part of Hawkular Metrics 0.22.0.Final
      o Note that 0.22.0.Final will begin packaging the E-mail and
        Webhook Alerting Action Plugins!
  * Soon as part of Hawkular Services (supporting ManageIQ)
      o When Hawkular Services upgrades to Metrics 0.22.0.Final
        (predicted with Services 0.22.0.Final)


For more details about this release: 
https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12315924&version=12331986

Hawkular Alerting Team
    Jay Shaughnessy (jshaughn at redhat.com)
    Lucas Ponce (lponce at redhat.com)





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161130/d7b5f606/attachment.html 

From fbrychta at redhat.com  Wed Nov 30 12:01:23 2016
From: fbrychta at redhat.com (Filip Brychta)
Date: Wed, 30 Nov 2016 12:01:23 -0500 (EST)
Subject: [Hawkular-dev] Please rebase your open h-metrics PRs on master
In-Reply-To: <805966925.459265.1480524610644.JavaMail.zimbra@redhat.com>
Message-ID: <1762392877.461134.1480525283960.JavaMail.zimbra@redhat.com>

Hello,
https://github.com/hawkular/hawkular-metrics/pull/704 which introduced some breaking changes for our perf tests CI has been merged.
Our jenkins jobs are updated but changes are not backward compatible so the job will fail with older PRs.
Please rebase your open PRs on master. Newly created PRs should work correctly.

Filip

From hrupp at redhat.com  Tue Nov 29 12:58:02 2016
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Tue, 29 Nov 2016 12:58:02 -0500
Subject: [Hawkular-dev] Srcdeps - some changes to come
In-Reply-To: <4ef3c749-a0fe-9296-a36a-3c159f8e22ce@redhat.com>
References: <4ef3c749-a0fe-9296-a36a-3c159f8e22ce@redhat.com>
Message-ID: <676C3549-A450-411A-A70B-F01CEB7E1DCE@redhat.com>

Peter,
sounds good.
Thanks for all your efforts in that area

   Heiko

On 24 Nov 2016, at 10:26, Peter Palaga wrote:

> Hi *,
>
> I was able to invest some time into srcdeps in the recent couple of
> months. Srcdeps is now a bit more powerful - esp. it is able to handle
> all kinds of dependencies incl. parents and BoM imports. The new
> functionality was enabled by using the Maven Core Extensions API 
> instead
> of Maven Plugin API.
>
> Technically, srcdeps now provides its own custom implementation of 
> Maven
> Local Repository [1]. In this way srcdeps is able to intercept every
> single request to the Maven Local Repository and eventually build the
> requested artifact from source and install it locally if necessary.
>
> The convention to declare a source dependencies using
> -SRC-revision-{sha1} suffix stayed unchanged. However, the mapping 
> from
> GAVs to git repositories now lives in .mvn/srcdeps.yaml file rather 
> than
> in pom.xml file.
>
> In the coming weeks, I'll be preparing PRs to migrate from the old
> srcdeps-maven-plugin to the new srcdeps core extension.
>
> I'll also introduce mvnw (a.k.a. Maven Wrapper [2]) so that there is a
> common way for developers, CI and srcdeps to get the same clearly
> defined version of Maven.
>
> Are there any concerns or questions?
>
> [1] https://github.com/srcdeps/srcdeps-maven
> [2] https://github.com/takari/maven-wrapper#maven-wrapper
>
> Thanks,
>
> Peter
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev


-- 
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht M?nchen HRB 153243
Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, 
Eric Shander

From mazz at redhat.com  Wed Nov 30 23:11:22 2016
From: mazz at redhat.com (John Mazzitelli)
Date: Wed, 30 Nov 2016 23:11:22 -0500 (EST)
Subject: [Hawkular-dev] hawkular wildfly agent release with jmx support
In-Reply-To: <685855725.697961.1480565313515.JavaMail.zimbra@redhat.com>
Message-ID: <662518062.698022.1480565482072.JavaMail.zimbra@redhat.com>

Hawkular WildFly Agent 0.25.0.Final was just released - this has Jolokia support put back in, as well as new local JMX support. So this means just like we have remote and local DMR managed servers, we now have remote and local JMX managed servers.

There are integration tests that test both Jolokia and local JMX support.