You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, it falls short when trying to debug messages coming from multiple different models - all of these will be assigned the mlserver name so it's difficult to tell which message came from which component.. A workaround is to roll your own logging in each component, but this adds boilerplate for each of the components that require logging (unless the custom logging configuration is split out into some utility library, but then that brings in other complications).
The text was updated successfully, but these errors were encountered:
An option to add the model name to the mlserver logs will be useful for my project's use case as well. It gets quite difficult to differentiate the logs from different models, especially as the number of models loaded into the same mlserver instance grows.
May I know if there are any plans to add such a feature in the near future?
Using the built-in logger is convenient because it's auto-configured:
MLServer/mlserver/logging.py
Line 23 in 7437787
However, it falls short when trying to debug messages coming from multiple different models - all of these will be assigned the
mlserver
name so it's difficult to tell which message came from which component.. A workaround is to roll your own logging in each component, but this adds boilerplate for each of the components that require logging (unless the custom logging configuration is split out into some utility library, but then that brings in other complications).The text was updated successfully, but these errors were encountered: