Open jblachly opened 1 year ago
another data point here, we're using salsa at Apollo in the context of the apollo-rs graphql compiler tools, that is now going in our router, and these logs are very noisy. In general libraries tend to avoid logging at higher levels than debug or trace, and leave the rest to the main application.
I see that the src/derived/slot.rs
file is not present on master, but there are still some info!()
calls in recent files: https://github.com/salsa-rs/salsa/commit/356392578bb86d2aa287940bfe95ae6355f286a3#diff-f520734994fdb4b1ea8c2e1082b3676aa8f09e3af82d5e118fa5bf483b243be5R35
Problem Statement Salsa is verbosely logging query and computation events at the INFO level which makes it hard to find info from client libraries or applications in the logs.
Background and Motivation I am using citeproc-rs to render bibliographic citations into HTML; citeproc-rs uses salsa for computation of the citation style language (CSL).
I've written a service that accepts CSL and renders the citation to HTML and returns it. Below is an example of a single query for a single reference: (note that all but the first 3 lines originate in salsa)
Question Are you amenable to decreasing these messages to the TRACING or DEBUG level? If yes, is the current, non-2022 salsa accepting changes?
Thanks in advance