Removing Syslog UI from UCP Docs as this feature has been EOLd

_data/toc.yaml

@@ -1190,8 +1190,6 @@ manuals:
           title: Run only the images you trust
         - path: /ee/ucp/admin/configure/set-session-timeout/
           title: Set the user's session timeout
-        - path: /ee/ucp/admin/configure/store-logs-in-an-external-system/
-          title: Store logs in an external system
         - path: /ee/ucp/admin/configure/ucp-configuration-file/
           title: UCP configuration file
         - path: /ee/ucp/admin/configure/use-node-local-network-in-swarm/

ee/ucp/admin/configure/add-labels-to-cluster-nodes.md

@@ -142,4 +142,5 @@ You can add or remove deployment constraints on this page.
 
 ## Where to go next
 
-- [Store logs in an external system](store-logs-in-an-external-system.md)
+- [Collect UCP Cluster Metrics with Prometheus](collect-cluster-metrics.md)
+- [Configure UCP Audit Logging](create-audit-logs.md)

ee/ucp/admin/configure/store-logs-in-an-external-system.md

@@ -1,64 +0,0 @@
----
-title: Configure UCP logging
-description: Learn how to configure Docker Universal Control Plane to store your logs
-  on an external log system and configure appropriate log levels.
-keywords: ucp, integrate, logs
----
-
-You can configure UCP's log level and destination for sending logs to a remote logging service:
-
-1. Log in to UCP with an administrator account.
-2. Navigate to the **Admin Settings** page.
-3. Set the information about your logging server, and click
-   **Save**.
-
-![](../../images/configure-logs-1.png){: .with-border}
-
-> External system for logs
->
-> Administrators should configure Docker EE to store logs using an external
-> system. By default, the Docker daemon doesn't delete logs, which means that
-> in a production system with intense usage, your logs can consume a
-> significant amount of disk space, especially when configured at DEBUG level.
-{: .important}
-
-## Example: Setting up an ELK stack
-
-One popular logging stack is composed of Elasticsearch, Logstash, and
-Kibana. The following example demonstrates how to set up an example
-deployment which can be used for logging.
-
-```none
-docker volume create --name orca-elasticsearch-data
-
-docker container run -d \
-    --name elasticsearch \
-    -v orca-elasticsearch-data:/usr/share/elasticsearch/data \
-    elasticsearch elasticsearch -Enetwork.host=0.0.0.0
-
-docker container run -d \
-    -p 514:514 \
-    --name logstash \
-    --link elasticsearch:es \
-    logstash \
-    sh -c "logstash -e 'input { syslog { } } output { stdout { } elasticsearch { hosts => [ \"es\" ] } } filter { json { source => \"message\" } }'"
-
-docker container run -d \
-    --name kibana \
-    --link elasticsearch:elasticsearch \
-    -p 5601:5601 \
-    kibana
-```
-
-Once you have these containers running, configure UCP to send logs to
-the IP of the Logstash container. You can then browse to port 5601 on the system
-running Kibana and browse log/event entries. You should specify the "time"
-field for indexing.
-
-When deployed in a production environment, you should secure your ELK
-stack. UCP does not do this itself, but there are a number of 3rd party
-options that can accomplish this, like the Shield plug-in for Kibana.
-
-## Where to go next
-
-- [Restrict services to worker nodes](restrict-services-to-worker-nodes.md)