1 files changed, 11 insertions, 11 deletions
diff --git a/docs/Logging_Enhancements_Project/logging_enhancements_project.rst b/docs/Logging_Enhancements_Project/logging_enhancements_project.rst
index c74535a..81476f0 100644
--- a/docs/Logging_Enhancements_Project/logging_enhancements_project.rst
+++ b/docs/Logging_Enhancements_Project/logging_enhancements_project.rst
@@ -81,7 +81,7 @@ components involved in its processing.
 A reference configuration of \ `*Elastic
 Stack * <https://www.elastic.co/products>`__\ can be deployed
 using \ `*ONAP Operations
-Manager* <https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project>`__.
+Manager* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16230609/ONAP+Operations+Manager+Project>`__.
 
 This document gives conventions you can follow to generate conformant,
 indexable logging output from your component.
@@ -121,7 +121,7 @@ EELF is a facade, so logging output is configured in two ways:
 
 2. By way of a provider configuration document,
    typically \ **logback.xml** or **log4j.xml**.
-   See \ `*Providers* <https://wiki.onap.org/display/DW/ONAP+Application+Logging+Guidelines+v1.1#ONAPApplicationLoggingGuidelinesv1.1-Providers>`__.
+   See \ `*Providers* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16245051/ONAP+Application+Logging+Guidelines+v1.1>`__.
 
 
 **SLF4J**
@@ -151,7 +151,7 @@ abstracted behind EELF or SLF4J, it may not be worth the effort.
 
 Logback is the most commonly used provider. It is generally configured
 by an XML document named \ **logback.xml**.
-See \ `*Configuration* <https://wiki.onap.org/display/DW/ONAP+Application+Logging+Guidelines+v1.1#ONAPApplicationLoggingGuidelinesv1.1-Configuration>`__.
+See \ `*Configuration* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16245051/ONAP+Application+Logging+Guidelines+v1.1>`__.
 
 
 **Log4j 2.X**
@@ -159,7 +159,7 @@ See \ `*Configuration* <https://wiki.onap.org/display/DW/ONAP+Application+Loggin
 
 Log4j 2.X is somewhat less common than Logback, but equivalent. It is
 generally configured by an XML document
-named \ **log4j.xml**. See \ `*Configuration* <https://wiki.onap.org/display/DW/ONAP+Application+Logging+Guidelines+v1.1#ONAPApplicationLoggingGuidelinesv1.1-Configuration>`__.
+named \ **log4j.xml**. See \ `*Configuration* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16245051/ONAP+Application+Logging+Guidelines+v1.1>`__.
 
 
 **Log4j 1.X**
@@ -171,10 +171,10 @@ machine-readable. See \ `*https://logging.apache.org/log4j/1.2/* <https://loggin
 
 This affects existing OpenDaylight-based components like SDNC and APPC,
 since ODL releases prior
-to \ `*Carbon* <https://www.opendaylight.org/what-we-do/current-release>`__ bundle
+to \ `*Carbon* <https://docs.opendaylight.org/en/latest/release-notes/>`__ bundle
 Log4j 1.X, and make it difficult to replace. The \ `*Common Controller
 SDK
-Project* <https://wiki.onap.org/display/DW/Common+Controller+SDK+Project>`__ project
+Project* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16230653/Common+Controller+SDK+Project>`__ project
 targets ODL Carbon, so the problem should resolve in time.
 
 What to Log
@@ -231,7 +231,7 @@ A Mapped Diagnostic Context (MDC) allows an arbitrary string-valued
 attribute to be attached to a Java thread. The MDC's value is then
 emitted with each log message. The set of MDCs associated with a log
 message is serialized as unordered name-value pairs (see `*Text
-Output* <https://wiki.onap.org/display/DW/ONAP+Application+Logging+Guidelines+v1.1#ONAPApplicationLoggingGuidelinesv1.1-TextOutput>`__).
+Output* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16245051/ONAP+Application+Logging+Guidelines+v1.1>`__).
 
 A good discussion of MDCs can be found
 at \ `*https://logback.qos.ch/manual/mdc.html* <https://logback.qos.ch/manual/mdc.html>`__.
@@ -976,24 +976,24 @@ You must:
 1. Choose a Logging provider and/or EELF. Decisions, decisions.
 
 2. Create a configuration file based on an existing
-   archetype. See \ `*Configuration* <https://wiki.onap.org/display/DW/ONAP+Application+Logging+Guidelines+v1.1#ONAPApplicationLoggingGuidelinesv1.1-Configuration>`__.
+   archetype. See \ `*Configuration* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16245051/ONAP+Application+Logging+Guidelines+v1.1>`__.
 
 3. Read your configuration file when your components initialize logging.
 
 4. Write logs to a standard location so that they can be shipped by
    Filebeat for indexing. See \ `*Output
-   Location* <https://wiki.onap.org/display/DW/ONAP+Application+Logging+Guidelines+v1.1#ONAPApplicationLoggingGuidelinesv1.1-OutputLocation>`__.
+   Location* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16245051/ONAP+Application+Logging+Guidelines+v1.1>`__.
 
 5. Report transaction state:
 
    a. Retrieve, default and propagate \ **RequestID**. See \ `*MDC -
-      RequestID* <https://wiki.onap.org/display/DW/ONAP+Application+Logging+Guidelines+v1.1#ONAPApplicationLoggingGuidelinesv1.1-MDC-RequestID>`__.
+      RequestID* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16245051/ONAP+Application+Logging+Guidelines+v1.1>`__.
 
    b. At each invocation of one ONAP component by another:
 
       i.   Initialize and propagate \ **InvocationID**. See \ `*MDC -
            Invocation
-           ID* <https://wiki.onap.org/display/DW/ONAP+Application+Logging+Guidelines+v1.1#ONAPApplicationLoggingGuidelinesv1.1-MDC-InvocationID>`__.
+           ID* <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16245051/ONAP+Application+Logging+Guidelines+v1.1>`__.
 
       ii.  Report \ **INVOKE** and **SYNCHRONOUS** markers in caller.