Aaron Lindsey created GEODE-8077:
------------------------------------
Summary: Logging to Standard Out
Key: GEODE-8077
URL: https://issues.apache.org/jira/browse/GEODE-8077
Project: Geode
Issue Type: Improvement
Components: logging
Reporter: Aaron Lindsey
The description below is from RFC [Logging to Standard Out
|[https://cwiki.apache.org/confluence/display/GEODE/Logging+to+Standard+Out]]
{quote}
h2. Problem
Currently logging to stdout is not consistent between client, server and
locator. If {{log-file}} is {{null}} on a client then it will log to stdout by
default, but on servers and locators it will log to a file named after the
member. Setting the {{log-file}} to {{""}} (empty string) on the server will
result in logging to stdout, but on a locator it is treated like the {{null}}
case and logs to a file. The only way get the locator to log to stdout is to
override the log4j.xml file.
h3. Anti-Goals
Do not change the current default behavior in client, server, or locators when
handling {{null}} or {{""}} (empty string).
h2. Solution
Introduce a new value {{log-file}} of {{"-"-}} (dash) to indicate standard out,
which is a common standard across most applications. When the logger is
configured and thee {{log-file}} value is {{""}} then the logger will log to
standard out and not to any files.
h3. Changes and Additions to Public Interface
Changes will be needed in documentation to reference this new value for logging
to standard out.
h3. Performance Impact
As no changes will be made to logging itself there is not impact to performance.
h3. Backwards Compatibility and Upgrade Path
Since no changes are being made to the current behaviors there should be no
impact to rolling upgrades and backwards compatibility.
{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
