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

[Feature] Allow orgId setting when integrating to external Grafana. #3818

Open
2 tasks done
gomgomshrimp opened this issue Jan 23, 2025 · 0 comments
Open
2 tasks done
Labels
enhancement New feature or request needs-triage

Comments

@gomgomshrimp
Copy link

gomgomshrimp commented Jan 23, 2025

Problem Statement

When integrating an external Grafana, if orgId is not 1, the link cannot be used.

I set up an external Grafana address in kubecost like this:
Image

Links from kubecost to Grafna have an orgId fixed to 1.
However, the Grafana I use uses a different orgId value, so I have to access it as 38.

# Links from kubecost
https://grafana.lgeinfra.com/d/at-cost-analysis-pod/pod-cost-and-utilization-metrics?orgId=1&...
# Links to actually access
https://grafana.lgeinfra.com/d/at-cost-analysis-pod/pod-cost-and-utilization-metrics?orgId=38&...

If I just change the orgId, the link works fine.

Solution Description

Optionally add a way to set orgId when using external grafana.

Alternatives

No response

Additional Context

No response

Troubleshooting

  • I have read and followed the issue guidelines and this is a feature request only for the Helm chart.
  • I have searched other issues in this repository and mine is not recorded.
@gomgomshrimp gomgomshrimp added enhancement New feature or request needs-triage labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-triage
Projects
None yet
Development

No branches or pull requests

1 participant