Hi All,
When I tried as mentioned in documentation [1] to access cluster metrics
(resource usage) through the REST endpoints it gives null values. But the
data is passed to the storage backend, "InfluxDB" when I checked the data
tables in the database.

AFAIU there are missed configurations in the "Heapster" that I currently
use, which comes in default in Kubernetes. As suggested by Manjula, the
current approach is to delete the "Heapster" pod and re- create the pod
with correct configurations. I would highly appreciate your suggestions on
this approach.

[1] https://github.com/kubernetes/heapster/blob/master/docs/model.md
Thank you.

On Mon, Mar 14, 2016 at 11:24 AM, Malmee Weerasinghe <[email protected]>
wrote:

> Hi All,
> I am working on building a dashboard for resource level monitoring of the
> pods in kubernetes used by AppCloud.
>
> In kubernetes this is the structure used for resource usage monitoring. 
> cAdvisor
> auto-discovers all containers in a node and collects CPU, memory,
> filesystem, and network usage statistics while Heapster queries all these
> data from the nodes through Kubelet and Kubelet gives the data fetched from
> the cAdvisor.
>
> I have studied on connecting to the cAdvisor and the cAdvisor UI which
> gives all the resource usage data of containers in a node graphically. But
> accessing these data through Heapster would be a better approach as
> suggested by Manjula than accessing a node seperately.
>
> I am studing on how to access these data through Heapster and how to pump
> the data received from cAdvisor API to the dashboard that is to be
> implemented.
>
> This is the approach that I will be taking and would highly appreciate
> your suggestions on this.
>
>
> ​
> Thank you
> --
> Malmee Weerasinghe
> WSO2 Intern
> mobile : (+94)* 71 7601905* |   email :   <[email protected]>
> [email protected]
>



-- 
Malmee Weerasinghe
WSO2 Intern
mobile : (+94)* 71 7601905* |   email :   <[email protected]>
[email protected]
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to