February 2, 2024
Control logging level
We’ve added a save
flag to all of our endpoints that generate logs on Humanloop so that you can control whether the request and response payloads that may contain sensitive information are persisted on our servers or not.
If save
is set to false
then no inputs
, messages
our outputs
of any kind (including the raw provider request and responses) are stored on our servers. This can be helpful for sensitive use cases where you can’t for example risk PII leaving your system.
Details of the model configuration and any metadata you send are still stored. Therefore you can still benefit from certain types of evaluators such as human feedback, latency and cost, as well as still track important metadata over time that may not contain sensitive information.
This includes all our chat and completion endpoint variations, as well as our explicit log endpoint.
Logging provider request
We’re now capturing the raw provider request body alongside the existing provider response for all logs generated from our deployed endpoints.
This provides more transparency into how we map our provider agnostic requests to specific providers. It can also effective for helping to troubleshoot the cases where we return well handled provider errors from our API.