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
{{ message }}
This repository has been archived by the owner on May 12, 2021. It is now read-only.
With Clear Containers, we have adopted the informal standard of adding a source= log field that allows consumers of log files to know where the log message ultimately originated.
By adding such a field, it will be obvious which log messages generated by the proxy came from the proxy itself and which came from the agent.
The text was updated successfully, but these errors were encountered:
Add a new "source" log field to allow logs coming from the agent to be
distinguished from logs coming direct from the proxy.
Fixeskata-containers#51.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Add a new "source" log field to allow logs coming from the agent to be
distinguished from logs coming direct from the proxy.
Fixeskata-containers#51.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Add a new "source" log field to allow logs coming from the agent to be
distinguished from logs coming direct from the proxy.
Fixeskata-containers#51.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
With Clear Containers, we have adopted the informal standard of adding a
source=
log field that allows consumers of log files to know where the log message ultimately originated.By adding such a field, it will be obvious which log messages generated by the proxy came from the proxy itself and which came from the agent.
The text was updated successfully, but these errors were encountered: