Repository navigation
[Bug]: Wrong Metrics for lava_provider_frozen_status #2048
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
Querying our provider using lavap q pairing provider lava@1nag7u4vmj95nsvvjk663a3vvn4l3ytt2jesnpd shows that we have 0 amount staked on AVAX chain currently, still it is showing on metrics as frozen: lava_provider_frozen_status{chainID="AVAX"} 1
Also, it is confusing why it is showing on explorer with 100 LAVA self staked. Is there a UI issue here also? Check image and link below:
https://info-mainnet.lavanet.xyz/provider/lava@1nag7u4vmj95nsvvjk663a3vvn4l3ytt2jesnpd
Lava Version
5.3.0
How to reproduce?
When querying the provider metrics, for example using curl localhost:7784/metrics | grep "lava_provider_frozen_status" we get this result for our providers. But if our provider has 0 amount staked how can it be frozen? The status should be 0 for AVAX chain, right?
# HELP lava_provider_frozen_status Frozen: 1, Not Frozen: 0
# TYPE lava_provider_frozen_status gauge
lava_provider_frozen_status{chainID="ARBITRUM"} 0
lava_provider_frozen_status{chainID="ARBITRUMS"} 0
lava_provider_frozen_status{chainID="AVAX"} 1
lava_provider_frozen_status{chainID="AXELAR"} 0
lava_provider_frozen_status{chainID="BASE"} 0
lava_provider_frozen_status{chainID="ETH1"} 0
lava_provider_frozen_status{chainID="LAVA"} 0
lava_provider_frozen_status{chainID="MOVEMENT"} 0
lava_provider_frozen_status{chainID="POLYGON"} 0
lava_provider_frozen_status{chainID="STRK"} 0
Activity