Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
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

Fix error prometheus gauge metrics_azurerm_reservation.go #99

Merged
merged 2 commits into from
Mar 6, 2024
Merged

Fix error prometheus gauge metrics_azurerm_reservation.go #99

merged 2 commits into from
Mar 6, 2024

Conversation

PaulPowershell
Copy link
Contributor

Fix error prometheus gauge, attempt 5, actual 6

Fix error prometheus gauge, attempt 5, actual 6
@PaulPowershell
Copy link
Contributor Author

Hi @mblaschke, I fix an error on prometheus gauge for reservation.go :
panic: inconsistent label cardinality: expected 5 label values but got 6 in prometheus.Labels{"kind":"Reservation", "reservationID":"XXXXX", "reservationOrderID":"XXXX", "scope":"providers/Microsoft.Billing/billingAccounts/XXXXXX", "skuName":"Standard_D8ds_v5", "usageDate":"2024-03-04 00:00:00 +0000 UTC"}
i just delete scope from prometheus.labels, build and test with my own docker hub and now it's OK

@mblaschke
Copy link
Member

image

Copy link

sonarcloud bot commented Mar 6, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@mblaschke
Copy link
Member

scope label should be there, so i've added it to the label list which i totally forgot to do

@mblaschke mblaschke merged commit 32960d7 into webdevops:main Mar 6, 2024
3 checks passed
@PaulPowershell PaulPowershell deleted the patch-1 branch March 7, 2024 09:51
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 this pull request may close these issues.

2 participants