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
I was inquiring about suppressing some askar INFO level logs and after some feedback from Andrew and Wade discovered that setting the RUST_LOG level to warn should do that.
In our ACA-Py deployment I could see this environment variable is set to warning instead. Which doesn't seem to be right.
Andrew mentioned that the value could be warn or fine tuned with aries_askar=warn
I tried both of those manually in my env and they both did what I wanted (suppressing all the askar INFO logs about pool connections and session starts etc).
So depends on what is wanted for this Dockerfile, but existing warning is not having intended effect.
(Note: same issue in Indy Dockerfile if that one matters)
The text was updated successfully, but these errors were encountered:
I was inquiring about suppressing some askar INFO level logs and after some feedback from Andrew and Wade discovered that setting the RUST_LOG level to
warn
should do that.In our ACA-Py deployment I could see this environment variable is set to
warning
instead. Which doesn't seem to be right.We're not setting this in any Traction deployment vals for what I'm testing it in, so I'm fairly sure it's coming from a mistake in the Dockerfile here.
https://github.com/hyperledger/aries-cloudagent-python/blob/d705ca2fe9132fc5bdc07e427e10f74201bbfac2/docker/Dockerfile#L25
Andrew mentioned that the value could be
warn
or fine tuned witharies_askar=warn
I tried both of those manually in my env and they both did what I wanted (suppressing all the askar INFO logs about pool connections and session starts etc).
So depends on what is wanted for this Dockerfile, but existing
warning
is not having intended effect.(Note: same issue in Indy Dockerfile if that one matters)
The text was updated successfully, but these errors were encountered: