Report
The issue here is the current value is reported as zero according to keda scaledobject's hpa based on trigger scaler of type metrics-api. The correct value should be in range of quintillion.
Expected Behavior
The expected behavior is to report the exact quintillion value for number.
Actual Behavior
The actual behavior is consistently being reported for external metric as zero.
Steps to Reproduce the Problem
- Define metrics-api trigger that is based on metric whose true value is large (in range of quintillion).
- Describe the hpa and see the current value remains zero over time.
Logs from KEDA operator
Keda operator logs is not the issue here so it won't be that relevant...
KEDA Version
2.17.0
Kubernetes Version
1.32
Platform
Microsoft Azure
Scaler Details
Metrics-API
Would you be open to contributing a fix?
Maybe
Anything else?
Here is the screenshot of the true metric value reported on Grafana:

Report
The issue here is the current value is reported as zero according to keda scaledobject's hpa based on trigger scaler of type metrics-api. The correct value should be in range of quintillion.
Expected Behavior
The expected behavior is to report the exact quintillion value for number.
Actual Behavior
The actual behavior is consistently being reported for external metric as zero.
Steps to Reproduce the Problem
Logs from KEDA operator
Keda operator logs is not the issue here so it won't be that relevant...
KEDA Version
2.17.0
Kubernetes Version
1.32
Platform
Microsoft Azure
Scaler Details
Metrics-API
Would you be open to contributing a fix?
Maybe
Anything else?
Here is the screenshot of the true metric value reported on Grafana: