Hi Heiko,
We're definitely not at cruising speed and when we'll have a website
with docs and tutorials it will certainly be easier to get a picture of
the metrics components and how they work together.
So far the metrics artifacts are the following;
* The core library
Just a JAR with lets you read and write data to a Cassandra or memory
backend
* The web services application
A restful API on top of the core library. Depends on JAX-RS and CDI,
nothing else from the EE7 stack. We could get rid of the CDI dependency
with a little effort.
* The console application
HTML5/Javascript application, for now packaged as a WAR for convenience.
* The protocol translator
A standalone application which gathers data coming from popular
collectors and post it to the web services application.
With the exception of the core library which you can get from Maven
central repositories, they all can be downloaded from the releases page:
https://github.com/rhq-project/rhq-metrics/releases
Regards,
Thomas
Le 08/01/2015 17:19, Heiko Braun a écrit :
I think i’ve found it:
https://developer.jboss.org/en/rhq/next
> On 08 Jan 2015, at 17:14, Heiko Braun <ike.braun(a)googlemail.com
> <mailto:ike.braun@googlemail.com>> wrote:
>
> I did refer to wf-core to point to the base capabilities of wildfly.
> Nothing prevents you from building upon the full EE server (wildfly),
> although you probably won’t need all the stock components.
>
> But what you say about Hawkular is interesting. I wasn’t aware of this
> effort until Mazz brought it forward. Listening to what you say Jay,
> it seems I confused rhq.metrics with rhq.next.
>
> Can you point me to some documentation about the architecture and
> design decisions behind rhq.next? Is it correct to say that rhq.next
> will leverage some of the rhq.metrics components?
>
> Regards, HeikoB
>
>> On 08 Jan 2015, at 16:54, Jay Shaughnessy <jshaughn(a)redhat.com
>> <mailto:jshaughn@redhat.com>> wrote:
>>
>> HeikoB, as for Wildfly-core, we haven't really used that afaik, just
>> using Wildfly at this point because I'm not sure Wildfly-core was
>> quite ready last time we looked. Has that changed? I assume
>> wfly-core is much lighter that wfly, and that is the main advantage,
>> giving up the J2EE EAR/WAR support. etc. Perhaps both wfly-core and
>> wfly proper will both play a role going forward.
>
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel