Re: [Hawkular-dev] scope of the agent design
On 03/20/2015 07:07 PM, Thomas Segismont wrote:
Le 17/03/2015 16:50, Thomas Heute a écrit :
> I don't think we are on the same page regarding the focus of the
> project/product.
>
> Hawkular is targeted toward Red Hat Middleware management, for
> infrastructure management there are gazillion other solutions.
> We need "some" basic infrastructure management, for those basic needs a
> user shouldn't need to maintain a solution made of multiple puzzle pieces.
So in this thread we talked about what we want the user experience to be
(simple install, works across different systems) and what we don't the
developer experience to be (with the RHQ agent pain points in mind).
That's important but could we elaborate on the use cases we want to
solve in the next milestones?
- Monitor Middleware servers (Metrics/alerts) running either in
OpenShift (Online/Enterprise) or "on premise".
- "Basic" monitoring of the underlying infrastructure (CPU/Memory/Disk
of the host or kube/docker environment)
- Have an inventory to relates "resources": what runs where ?
- Operate/Provision servers: the "mutable kind" a la JON and the
"immutable" kind (with F8)
For the "kube/docker/OpenShift" environment, we'll go though this
kadvisor thing, this should collect CPU/Memory/disk about a docker image
(cAdvisor) + CPU/Memory/disk at a cluster level (heapster) + any metric
expose through JMX or DMR. IMO we should be able to read the same data
when our servers are running outside of that environment.
Thomas
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev