Currently Heapster stores in internal memory few minutes of data and allows queries that
request this data (through its REST-interface). The consume part will just request the
data from the HWKMETRICS instead.
- Micke
----- Original Message -----
From: "Thomas Heute" <theute(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Tuesday, June 14, 2016 4:09:40 PM
Subject: Re: [Hawkular-dev]
Hawkular.org
On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman(a)redhat.com > wrote:
Consumers is terrible word for any client, as they both consume as well as produce the
data.
Well that was actually reflecting the current state, we have "things" that feed
data to the server and "things" that consume data from the server. The client
libraries provide an API to feed and consume.
For example for Heapster, we currently produce the data, however at the moment I'm
creating a change that will consume the data from HWKMETRICS.
Why does it consume data now ?
Thomas
Integration / clients is far more used and known word, while consumer/producer is
something more specific and implies a design pattern.
- Micke