5:07 p.m.
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Friday, April 8, 2016 5:22:32 PM
Subject: Re: [Hawkular-dev] hawkular-agent, prometheus, openshift
> There are some endpoints used in OpenShift/Kubernetes that stores metrics
> using the Prometheus protocol. These endpoint expose metrics in which
> Prometheus (or something which understands the protocol) can then bring
> into
> their system. We are looking at potentially being able to read from these
> endpoint types, not being able to read from a Prometheus server itself.
Then it sounds more like we'd want to have some kind of plugin or component
inside Hawkular-Metrics itself so H-Metrics can just pull metrics in using
the Prometheus protocol (in addition to getting metrics pushed into it via
its REST API). This could be an optional component to Hawkular-Metrics for
those that don't need or want it. But it sounds like this is just another
protocol to insert data into H-Metrics.
I don't see this as something which should be part of Hawkular Metrics.
Essentially we are going to be dealing with people running various different types of
containers in their OpenShift environment. My tomcat server may be exposing metrics in the
jolokia format, my golang app over there might be exposing metrics in the prometheus
protocol, my other app somewhere else might be exposing their metrics in some other
protocol.
We need something to figure out where those endpoints are available from, gather the
metadata about the containers which are exposing those endpoints, convert the metrics from
one type into something Hawkular Metrics can understand, and then write those metrics
(with metadata based tags) into Hawkular Metrics.
I think this needs to be part of a separate component. There is going to be a lot of code
here dealing specifically with the OpenShift environment.
If we are reading from a jolokia endpoint and we have an agent which knows how to store
jolokia style metrics in Hawkular-Metrics, then we should of course try and reuse
components.