-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add target persona meta information to logs #3004
Labels
Comments
Superseded by structured logging in 2.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
As a datascientist I don't want my logs to be cluttered with devops infos.
Is your feature request related to a problem? Please describe.
Currently we do not separate logs according to the persona. devops infos (e.g. availability of
multiprocessing
,numba
, number of worker processes, telemetry) dilutes the logs a data scientist is interested in. Same applies for devops logs regarding data scientist infos (e.g. warnings about which similarity metric to use for some models).Describe the solution you'd like
We add extra
haystack_persona
to all logs:datascience
marks logs for data scientistsdevops
marks logs for devops/data engineershaystack_persona
is an array of values.Describe alternatives you've considered
Another distinction could be (user-facing vs. backend-applications) but although this has almost the same distribution it is way harder to grasp for notebook users.
Additional context
Main focus lies on bigger deployments using analytics and monitoring tools and a separate UI. Notebook users should also be able to make use of it. The value must be easily filtered for in standard
logging
andstructlog
.The text was updated successfully, but these errors were encountered: