chore(issues): Log warning instead of exception

[mrduncan]

We raise an exception when failing to parse a Snuba response, there is no need to also log an exception here since it otherwise results in 2 separate errors being logged for the same problem.

Fixes SENTRY-5AGR

See also SENTRY-5AGQ

[sentry]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: src/sentry/utils/snuba.py

Function	Unhandled Issue
_bulk_snuba_query	SnubaError: HTTPConnectionPool(host='snuba-api', port=80): Read timed out. (read timeout=30) ... Event Count: 3

[cursor]

Bug: Log Level Downgrade Masks Parsing Errors

Changing logger.exception() to logger.warning() for Snuba JSON parsing ValueErrors loses the original traceback and error details. This also downgrades the log level from ERROR to WARNING, potentially breaking monitoring and making these parsing failures much harder to debug.

 

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/sentry/utils/snuba.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #101368      +/-   ##
===========================================
+ Coverage   80.86%    81.01%   +0.15%     
===========================================
  Files        8696      8696              
  Lines      385725    385736      +11     
  Branches    24381     24381              
===========================================
+ Hits       311898    312509     +611     
+ Misses      73459     72859     -600     
  Partials      368       368