Relates #139883.
We were too noisy and generally logged exceptions during storing of async ESQL results as ERROR. This is getting downgraded to WARN in #142112.
However, the noise mostly comes from CBEs and rejected store requests because the result sets were too big. These are fine to log as WARN, but now we do not log genuine bugs (e.g. IllegalStateException) as ERROR; this is, however, required to ensure good alerting for bugs in async queries, esp. in Serverless.
We should probably do the same as #140905 and distinguish between exceptions based on their status:
- log 5xx exceptions as ERROR
- log other exceptions as WARN
Relates #139883.
We were too noisy and generally logged exceptions during storing of async ESQL results as ERROR. This is getting downgraded to WARN in #142112.
However, the noise mostly comes from CBEs and rejected store requests because the result sets were too big. These are fine to log as WARN, but now we do not log genuine bugs (e.g. IllegalStateException) as ERROR; this is, however, required to ensure good alerting for bugs in async queries, esp. in Serverless.
We should probably do the same as #140905 and distinguish between exceptions based on their status: