New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
empty screen #5
Comments
Provide your environment details.
and on you go. I also had an empty screen initially. Then waited a bit and here it goes .... Suggestion: Try sizing the screen/window of your shell/terminal and see if that refreshes and gives the content that |
im using latest murre, go version go1.18.3 linux/amd64, and debian/bash |
Did you try my suggestion ... sizing the terminal window? |
tried, did not help :/ |
hi, |
Uuuh that's interesting @ulrichSchreiner - That's the same scenario I'm in ( using |
Hey @ulrichSchreiner - We've created a fix for the env support which be added in our next release @dyipon - Can you please check if @ulrichSchreiner solution works for you? |
@maxlevinps I just updated to 0.0.3, and tried again: $ murre --kubeconfig ~/.kube/config but still nothing, I just get empty screen |
do you have a correct (working) i use kubie to manage different cluster configs and kubie creates temporary files with a config and sets in my case i do have a file |
don't know why, but it's started to working. |
Same issue here: maybe this should be better documented in the readme. |
Maybe can we reopen the issue and double check what happens in my case too?
and
and my pods
Finally
|
Tried with Lens, which is very smart and suggested me to install prometheus operator and the metric server Screencast.from.2022-12-06.21-58-42.webm
|
I've also enabled the metric server from minikube
but the table of murre is always empty. Is there a way to debug it or a verbose flag? What about reopening this issue to track the problem, at least? |
I've cloned the repo and built it after adding some fmt.Println to understand the flow. func (t *Table) getCell(stats *k8s.Stats, column int) *tview.TableCell {
fmt.Println("stats",stats.Namespace, stats.PodName, stats.ContainerName) even if I see the tick e the output before updateMetric fmt.Println("update Metrics!")
err = m.updateMetrics() I guess something goes wrong in between. Thank you for your help! Editgetting closer, it looks like the cpu array is empty output
from func (m *Murre) updateMetrics() error {
fmt.Println("here inside the func update Metrics")
metrics, err := m.fetcher.GetMetrics()
if err != nil {
return err
}
fmt.Println("metrics: ", metrics)
for _, node := range metrics {
fmt.Println("node CPU: ", node.Cpu, node.Timestamp)
m.updateCpu(node.Cpu, node.Timestamp)
m.updateMemory(node.Memory, node.Timestamp)
}
return nil
} But the Fetcher is getting the correct minikube node at least! So it's not a kubeconfig connection issue... output
from func (f *Fetcher) GetMetrics() ([]*NodeMetrics, error) {
fmt.Println("Fether is going to get the nodes!!!")
nodes, err := f.getNodes()
fmt.Println("nodes", nodes, "found")
if err != nil {
return nil, err
} Furthermore, it prints
from func (f *Fetcher) fetchMetricsFromNode(node string) (*NodeMetrics, error) {
fetchTime := time.Now()
path := fmt.Sprintf(CADVISOR_PATH_TEMPLATE, node)
fmt.Println("fetchMetricsFromNode",CADVISOR_PATH_TEMPLATE, node)
b, err := f.clientset.RESTClient().Get().AbsPath(path).Do(context.Background()).Raw()
fmt.Println("clientset.RESTClient",path,"b",b,"to be parsed") Now I have also double checked that
|
This is the issue! Would you be so kind to reopen it and consider it a TODO item? cpuMetric.CpuUsageSecondsTotal = metric.GetCounter().GetValue()
if cpuMetric.Name == "" || cpuMetric.PodName == "" || cpuMetric.Namespace == "" {
//todo - dont know why this happens
fmt.Println("***TODO*** - dont know why this happens")
continue
}
cpuMetrics = append(cpuMetrics, cpuMetric) That happens because of multi-container-pods, hence we need to traverse k8s metric API's tree structure, from the pod to the container. |
hello,
I just installed and started murre, but I just get an empty screen. Whats the best way to debug this issue?
The text was updated successfully, but these errors were encountered: