Skip to content
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

Opencost UI no values #490

Closed
marquesj2-ppb opened this issue Apr 24, 2024 · 10 comments · Fixed by #514
Closed

Opencost UI no values #490

marquesj2-ppb opened this issue Apr 24, 2024 · 10 comments · Fixed by #514

Comments

@marquesj2-ppb
Copy link

Hi,
Can't seem to get opencost to read any information when using 0.10.3 or 1.0.2 of this chart

Seems to be same case as #263 but can't get it to solve.

  opencost:
    opencost:
      ui:
        enabled: true
      exporter:
        defaultClusterId: 'Hrk8sDEV'
      prometheus:
        existingSecretName: prometheus-k8s-monitoring
        external:
          url: 'https://prometheus-us-central1.grafana.net/api/prom'

image

@dlahn
Copy link

dlahn commented Apr 25, 2024

@marquesj2-ppb What sort of results are you getting back when querying for node_ram_hourly_cost in Grafana?

@marquesj2-ppb
Copy link
Author

image
This is the metric explorer on grafana

@dlahn
Copy link

dlahn commented May 2, 2024

@marquesj2-ppb I think this will solve your issue: opencost/opencost-grafana-dashboard#2 (comment)

There does appear to be an issue with k8s-monitoring-helm regarding this, where it is re-writing the instance label which causes issues with Opencost.

@marquesj2-ppb
Copy link
Author

Should your solution be implemented in the base chart?
opencost/opencost-grafana-dashboard#2 (comment)

@petewall
Copy link
Collaborator

petewall commented May 6, 2024

I'm not sure what @dlahn 's fix is, but I think adding honor_labels = true to the code will help the issue. That will keep the instance label set by OpenCost as instance and not rename it to exported_instance, just to set instance to the OpenCost service name, which is not helpful.

@dlahn
Copy link

dlahn commented May 6, 2024

@petewall Your solution is the optimal one. I'm doing a bunch of renaming, which is not ideal :)

@petewall
Copy link
Collaborator

petewall commented May 6, 2024

Ah, relabel rules can be painful fun! haha. I'd love your eyes on the PR in a few minutes.

@petewall
Copy link
Collaborator

petewall commented May 6, 2024

I just released version 1.0.7 which should solve the instance label issue: https://github.com/grafana/k8s-monitoring-helm/releases/tag/v1.0.7

@marquesj2-ppb , let me know if this solved things for you.

@dlahn
Copy link

dlahn commented May 6, 2024

Seems good on my end as well. Thanks for the fix @petewall. I had been meaning to open an issue.

@marquesj2-ppb
Copy link
Author

Seems good here!
thanks a lot 🙇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants