Slackbot
01/31/2023, 8:09 AMSean
01/31/2023, 9:22 AMnewrelic-admin run-program uvicorn
.
Treating BentoML as a simple ASGI application will not work out-of-the-box. BentoML’s runner architecture spawns multiple processes to optimize system resource utilization. Instead of a single uvicorn process, BentoML consists of multiple ASGI processes.
I will need to look into New Relic further to investigate a better integration. Since BentoML is fully compliant to OpenTelemetry and Prometheus standards, I’m hopeful that New Relic has proper supports for those standards.Sean
01/31/2023, 9:30 AMI’m not seeing any evidence of errors, even though most of my requests were to theI think this is due to New Relic not recognizingendpoint/newrelic-error
bentoml.exceptions.InternalServerError
.
No trace ID in the response headers; with FastAPI the response headers include the trace ID. FastAPI also knows how to handle when the trace ID is present in the request headersAs discussed in an earlier thread, a better approach I think is to pass through callers trace context so the caller knows the Trace ID implicitly when errors happen. I think the gist of all these issues is the Python Agent. Again, I believe a better integration with New Relic is just around the corner.
Eric Riddoch
01/31/2023, 9:33 AMSean
01/31/2023, 9:53 AMSean
01/31/2023, 9:54 AMSean
01/31/2023, 10:00 AMEric Riddoch
01/31/2023, 10:02 AM/metrics
endpoint on a schedule and publishes those to NewRelic, that would be perfect.Eric Riddoch
01/31/2023, 10:02 AMEric Riddoch
01/31/2023, 10:03 AMEric Riddoch
02/06/2023, 10:39 PM