We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
2.3.2
1.28
EKS
Network Costs Metrics Grafana dashboard has incorrect query for Cross Region Data and Cross Zone Data panels have incorrect label names in queries.
Both panels are built using kubecost_pod_network_ingress_bytes_total metric as below:
kubecost_pod_network_ingress_bytes_total
Cross Region Data:
sum(increase(kubecost_pod_network_ingress_bytes_total {internet="false",namespace=~"$namespace",cluster_id=~"$cluster",pod_name=~"$pod_name", sameRegion="false",sameZone="false", service=~"$service"} [1h])) by($aggregation)
Cross Zone Data:
sum(increase(kubecost_pod_network_ingress_bytes_total {internet="false", namespace=~"$namespace", cluster_id=~"$cluster", pod_name=~"$pod_name", sameRegion="true", sameZone="false", service=~"$service"} [1h])) by($aggregation)
However, these queries have following typos:
sameZone
sameRegion
same_zone
same_region
service
Example metric from Kubecost Prometheus
If you agree that it is an issue, I am happy to work on fix :)
These panels should show actual data
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Kubecost Helm Chart Version
2.3.2
Kubernetes Version
1.28
Kubernetes Platform
EKS
Description
Network Costs Metrics Grafana dashboard has incorrect query for Cross Region Data and Cross Zone Data panels have incorrect label names in queries.
Both panels are built using
kubecost_pod_network_ingress_bytes_total
metric as below:Cross Region Data:
Cross Zone Data:
However, these queries have following typos:
kubecost_pod_network_ingress_bytes_total
metric has no labels such assameZone
andsameRegion
, but rathersame_zone
andsame_region
;service
label is not always available, so should be keep it in this dashboard? Or maybe metric has to be fixed with default value for this label?Example metric from Kubecost Prometheus
If you agree that it is an issue, I am happy to work on fix :)
Steps to reproduce
Expected behavior
These panels should show actual data
Impact
No response
Screenshots
No response
Logs
No response
Slack discussion
No response
Troubleshooting
The text was updated successfully, but these errors were encountered: