dachaostripe commented on issue #9545: URL: https://github.com/apache/pinot/issues/9545#issuecomment-1270773878
> If pinot broker returns the requestId and the brokerId along with the response/exception, will that help? This probably would help during testing and development where we can temporarily log the response, assuming broker AND online/offline servers also tag all their related logs with the broker id(in addition to requestId), which is still not as convenient as simply searching for requestId alone. And that still doesn't solve the problem in production where clients don't usually log the response, and especially in a larger company where the team that owns and maintains Pinot clusters doesn't necessarily also own the clients and cannot force client teams to log the responses(and that also sometimes violates company's security rules). In case of excessive errors from Pinot triggering the alarms, or a client team asking why some of their requests were failing, we don't have an effective way to correlate client and Pinot logs, and to definitively conclude what went wrong for a particular request. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
