[FAB-15658] Update doc for Gologging

Removed references for the shim logger from the Doc.
Replaced with a statement putting the onus of implementing
logging on the chaincode developer.

Signed-off-by: Brett Logan <Brett.T.Logan@ibm.com>
Change-Id: I160354a867f0d430142725e10da96c94b142e50c

Author: Brett Logan

docs/source/logging-control.rst

@@ -91,130 +91,33 @@ to print the logs in a human-readable console format. It can be also set to
 ``json`` to output logs in JSON format.
 
 
-Go chaincodes
--------------
+Chaincode
+---------
 
-The standard mechanism to log within a chaincode application is to
-integrate with the logging transport exposed to each chaincode instance
-via the peer. The chaincode ``shim`` package provides APIs that allow a
-chaincode to create and manage logging objects whose logs will be
-formatted and interleaved consistently with the ``shim`` logs.
+**Chaincode logging is the responsibility of the chaincode developer.**
 
-As independently executed programs, user-provided chaincodes may
-technically also produce output on stdout/stderr. While naturally useful
-for "devmode", these channels are normally disabled on a production
-network to mitigate abuse from broken or malicious code. However, it is
-possible to enable this output even for peer-managed containers (e.g.
-"netmode") on a per-peer basis via the
-CORE\_VM\_DOCKER\_ATTACHSTDOUT=true configuration option.
+As independently executed programs, user-provided chaincodes may technically
+also produce output on stdout/stderr. While naturally useful for “devmode”,
+these channels are normally disabled on a production network to mitigate abuse
+from broken or malicious code. However, it is possible to enable this output
+even for peer-managed containers (e.g. “netmode”) on a per-peer basis
+via the CORE_VM_DOCKER_ATTACHSTDOUT=true configuration option.
 
-Once enabled, each chaincode will receive its own logging channel keyed
-by its container-id. Any output written to either stdout or stderr will
-be integrated with the peer's log on a per-line basis. It is not
-recommended to enable this for production.
+Once enabled, each chaincode will receive its own logging channel keyed by its
+container-id. Any output written to either stdout or stderr will be integrated
+with the peer’s log on a per-line basis. It is not recommended to enable this
+for production.
 
-API
-~~~
-
-``NewLogger(name string) *ChaincodeLogger`` - Create a logging object
-for use by a chaincode
-
-``(c *ChaincodeLogger) SetLevel(level LoggingLevel)`` - Set the logging
-level of the logger
-
-``(c *ChaincodeLogger) IsEnabledFor(level LoggingLevel) bool`` - Return
-true if logs will be generated at the given level
-
-``LogLevel(levelString string) (LoggingLevel, error)`` - Convert a
-string to a ``LoggingLevel``
-
-A ``LoggingLevel`` is a member of the enumeration
-
-::
-
-    LogDebug, LogInfo, LogNotice, LogWarning, LogError, LogCritical
-
-which can be used directly, or generated by passing a case-insensitive
-version of the strings
-
-::
-
-    DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL
-
-to the ``LogLevel`` API.
-
-Formatted logging at various severity levels is provided by the
-functions
-
-::
-
-    (c *ChaincodeLogger) Debug(args ...interface{})
-    (c *ChaincodeLogger) Info(args ...interface{})
-    (c *ChaincodeLogger) Notice(args ...interface{})
-    (c *ChaincodeLogger) Warning(args ...interface{})
-    (c *ChaincodeLogger) Error(args ...interface{})
-    (c *ChaincodeLogger) Critical(args ...interface{})
-
-    (c *ChaincodeLogger) Debugf(format string, args ...interface{})
-    (c *ChaincodeLogger) Infof(format string, args ...interface{})
-    (c *ChaincodeLogger) Noticef(format string, args ...interface{})
-    (c *ChaincodeLogger) Warningf(format string, args ...interface{})
-    (c *ChaincodeLogger) Errorf(format string, args ...interface{})
-    (c *ChaincodeLogger) Criticalf(format string, args ...interface{})
-
-The ``f`` forms of the logging APIs provide for precise control over the
-formatting of the logs. The non-\ ``f`` forms of the APIs currently
-insert a space between the printed representations of the arguments, and
-arbitrarily choose the formats to use.
-
-In the current implementation, the logs produced by the ``shim`` and a
-``ChaincodeLogger`` are timestamped, marked with the logger *name* and
-severity level, and written to ``stderr``. Note that logging level
-control is currently based on the *name* provided when the
-``ChaincodeLogger`` is created. To avoid ambiguities, all
-``ChaincodeLogger`` should be given unique names other than "shim". The
-logger *name* will appear in all log messages created by the logger. The
-``shim`` logs as "shim".
-
-The default logging level for loggers within the Chaincode container can
-be set in the
-`core.yaml <https://github.com/hyperledger/fabric/blob/master/sampleconfig/core.yaml>`__
-file. The key ``chaincode.logging.level`` sets the default level for all
-loggers within the Chaincode container. The key ``chaincode.logging.shim``
-overrides the default level for the ``shim`` logger.
-
-::
-
-    # Logging section for the chaincode container
-    logging:
-      # Default level for all loggers within the chaincode container
-      level:  info
-      # Override default level for the 'shim' logger
-      shim:   warning
-
-The default logging level can be overridden by using environment
-variables. ``CORE_CHAINCODE_LOGGING_LEVEL`` sets the default logging
-level for all loggers. ``CORE_CHAINCODE_LOGGING_SHIM`` overrides the
-level for the ``shim`` logger.
-
-Go language chaincodes can also control the logging level of the
-chaincode ``shim`` interface through the ``SetLoggingLevel`` API.
-
-``SetLoggingLevel(LoggingLevel level)`` - Control the logging level of
-the shim
-
-Below is a simple example of how a chaincode might create a private
-logging object logging at the ``LogInfo`` level.
+Stdout and stderr not forwarded to the peer container can be viewed from the
+chaincode container using standard commands for your container platform.
 
 ::
 
-    var logger = shim.NewLogger("myChaincode")
+    docker logs <chaincode_container_id>
+    kubectl logs -n <namespace> <pod_name>
+    oc logs -n <namespace> <pod_name>
 
-    func main() {
 
-        logger.SetLevel(shim.LogInfo)
-        ...
-    }
 
 .. Licensed under Creative Commons Attribution 4.0 International License
    https://creativecommons.org/licenses/by/4.0/