kraken - Telegram chat flooded with rate limit messages

[ghost]

Describe the bug

When running a strategy that uses the kraken connector, and telegram_enabled, the telegram chat is flooded with messages relating to API rate limit.

For instance, the messages read:

(2024-04-29 15:19:55) API rate limit on /0/public/Ticker (1 calls per 1s) has almost reached. Limits used is 1 in the last 1 seconds

The current rate at which I am seeing these messages is somewhere along the lines of 2/minute.

Steps to reproduce

1. modify scripts/fixed_grid.py to use kraken connector
2. setup telegram integration
3. start bot using the modified fixed_grid.py script

Release version

1.27.0

Type of installation

Docker

Attach required files

No response

[Sengoku11]

Recently have the same API rate limit on REQUEST_WEIGHT has almost reached error. Didn't use kraken connector in strategies.

[Sengoku11]

Pure Market Making strategy with hitbtc connector.

[ghost]

hmmm, I think this might be a shared issue? the below snippet may be the culprit? what's the solution here? lower the level of these messages so they only go to logs instead of telegram ?

hummingbot/hummingbot/core/api_throttler/async_throttler.py

Lines 35 to 43 in a9d6d99

	if capacity_used + weight > rate_limit.limit:
	if self._last_max_cap_warning_ts < now - MAX_CAPACITY_REACHED_WARNING_INTERVAL:
	msg = f"API rate limit on {rate_limit.limit_id} ({rate_limit.limit} calls per " \
	f"{rate_limit.time_interval}s) has almost reached. Limits used " \
	f"is {capacity_used} in the last " \
	f"{rate_limit.time_interval} seconds"
	self.logger().notify(msg)
	AsyncRequestContextBase._last_max_cap_warning_ts = now
	return False

[Sengoku11]

@rapcmia I guess the issue is with binance oracle

[xiawu]

For a workaround, you can use the coin_cap as the oracle source.