Slackbot
01/31/2023, 7:38 AMSean
01/31/2023, 8:08 AMEric Riddoch
01/31/2023, 8:12 AM500 is the only error I can think of that would be useful at the moment.
• We've seen that Bento returns 503 when it gets overwhelmed
• We run it behind AWS API Gateway with Auth0 as an authorizer so 401 and 403 codes are taken care of for us.
The main thing I'd want is to be able to return a description of what happened in the response message, and a trace-id in the headers (which wasn't present when I tried raising an bentoml.exceptions.InternalServerError just now)Sean
01/31/2023, 8:32 AMSean
01/31/2023, 8:34 AMEric Riddoch
01/31/2023, 8:35 AMEric Riddoch
01/31/2023, 8:36 AMIt's possible to put a config to allow message pass throughIs there documentation on this?
Eric Riddoch
01/31/2023, 8:37 AMThe caller can pass through its own trace IDI know Bento supports OpenTelemetry, does that include automatically propagating the "baggage" headers, including picking up the trace/span ID from request headers and using that one in log statements?
Sean
01/31/2023, 8:38 AMI know Bento supports OpenTelemetry, does that include automatically propagating the “baggage” headers, including picking up the trace/span ID from request headers and using that one in log statements?Yes. It will respect the trace context passed in and emit the parent-child span correctly.
Sean
01/31/2023, 8:40 AMIs there documentation on this?Sorry I might have confused you. I meant that this feature, i.e. server error message passthrough, does not exist yet. It can be implemented by adding a config flag.
Eric Riddoch
01/31/2023, 8:49 AM