Skip to content

Commit cce2e45

Browse files
alchemyDocsalchemyDocs
committed
Rachael L. Graham: Merge pull request #4513 from alchemy-containers/rlg-logs-deprecate
1 parent c5ac61c commit cce2e45

10 files changed

+31
-255
lines changed

‎cs_at_events.md

+1-4
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2017, 2019
5-
lastupdated: "2019-09-25"
5+
lastupdated: "2019-10-01"
66

77
keywords: kubernetes, iks, audit
88

@@ -34,9 +34,6 @@ You can view, manage, and audit user-initiated activities in your {{site.data.ke
3434
You can also collect Kubernetes API audit logs from your cluster and forward them to {{site.data.keyword.la_full_notm}}. To access Kubernetes audit logs, you must [create an audit webhook in your cluster](/docs/containers?topic=containers-health#webhook_logdna).
3535
{: tip}
3636

37-
Previously, you could collect and forward audit logs to {{site.data.keyword.cloudaccesstrailfull_notm}} with LogAnalysis. As of 30 April 2019, you cannot provision new {{site.data.keyword.loganalysisshort_notm}} instances, and all Lite plan instances are deleted. Existing premium plan instances are supported until 30 September 2019. To continue collecting audit logs for your cluster, you must set up {{site.data.keyword.at_full_notm}}.
38-
{: deprecated}
39-
4037
## Tracking cluster management events
4138
{: #cluster-events}
4239

‎cs_firewall.md

+2-63
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2014, 2019
5-
lastupdated: "2019-09-26"
5+
lastupdated: "2019-10-01"
66

77
keywords: kubernetes, iks, firewall, vyatta, ips
88

@@ -347,71 +347,10 @@ If you have a firewall on the public network in your IBM Cloud infrastructure ac
347347
- `TCP port 443 FROM <each_worker_node_publicIP> TO https://iam.bluemix.net`
348348
- `TCP port 443 FROM <each_worker_node_publicIP> TO https://iam.cloud.ibm.com`
349349
350-
5. Optional: Allow outgoing network traffic from the worker nodes to {{site.data.keyword.monitoringlong_notm}}, {{site.data.keyword.loganalysislong_notm}}, Sysdig, and LogDNA services:
351-
* **{{site.data.keyword.monitoringlong_notm}}**:
352-
<pre class="screen">TCP port 443, port 9095 FROM &lt;each_worker_node_public_IP&gt; TO &lt;monitoring_subnet&gt;</pre>
353-
Replace <em>&lt;monitoring_subnet&gt;</em> with the subnets for the monitoring regions to which you want to allow traffic:
354-
<p><table summary="The first row in the table spans both columns. The rest of the rows should be read left to right, with the server zone in column one and IP addresses to match in column two.">
355-
<caption>IP addresses to open for monitoring traffic</caption>
356-
<thead>
357-
<th>{{site.data.keyword.containerlong_notm}} region</th>
358-
<th>Monitoring address</th>
359-
<th>Monitoring subnets</th>
360-
</thead>
361-
<tbody>
362-
<tr>
363-
<td>EU Central</td>
364-
<td><code>metrics.eu-de.bluemix.net</code></td>
365-
<td><code>158.177.65.80/30</code></td>
366-
</tr>
367-
<tr>
368-
<td>UK South</td>
369-
<td><code>metrics.eu-gb.bluemix.net</code></td>
370-
<td><code>169.50.196.136/29</code></td>
371-
</tr>
372-
<tr>
373-
<td>US East, US South, AP North, AP South</td>
374-
<td><code>metrics.ng.bluemix.net</code></td>
375-
<td><code>169.47.204.128/29</code></td>
376-
</tr>
377-
</tbody>
378-
</table></p>
350+
5. Optional: Allow outgoing network traffic from the worker nodes to Sysdig and LogDNA services:
379351
* **{{site.data.keyword.mon_full_notm}}**:
380352
<pre class="screen">TCP port 443, port 6443 FROM &lt;each_worker_node_public_IP&gt; TO &lt;sysdig_public_IP&gt;</pre>
381353
Replace <em>&lt;sysdig_public_IP&gt;</em> with the [Sysdig IP addresses](/docs/services/Monitoring-with-Sysdig?topic=Sysdig-network#network).
382-
* **{{site.data.keyword.loganalysislong_notm}}**:
383-
<pre class="screen">TCP port 443, port 9091 FROM &lt;each_worker_node_public_IP&gt; TO &lt;logging_public_IP&gt;</pre>
384-
Replace <em>&lt;logging_public_IP&gt;</em> with all of the addresses for the logging regions to which you want to allow traffic:
385-
<p><table summary="The first row in the table spans both columns. The rest of the rows should be read left to right, with the server zone in column one and IP addresses to match in column two.">
386-
<caption>IP addresses to open for logging traffic</caption>
387-
<thead>
388-
<th>{{site.data.keyword.containerlong_notm}} region</th>
389-
<th>Logging address</th>
390-
<th>Logging IP addresses</th>
391-
</thead>
392-
<tbody>
393-
<tr>
394-
<td>US East, US South</td>
395-
<td><code>ingest.logging.ng.bluemix.net</code></td>
396-
<td><code>169.48.79.236</code><br><code>169.46.186.113</code></td>
397-
</tr>
398-
<tr>
399-
<td>UK South</td>
400-
<td><code>ingest.logging.eu-gb.bluemix.net</code></td>
401-
<td><code>169.50.115.113</code></td>
402-
</tr>
403-
<tr>
404-
<td>EU Central</td>
405-
<td><code>ingest-eu-fra.logging.bluemix.net</code></td>
406-
<td><code>158.177.88.43</code><br><code>159.122.87.107</code></td>
407-
</tr>
408-
<tr>
409-
<td>AP South, AP North</td>
410-
<td><code>ingest-au-syd.logging.bluemix.net</code></td>
411-
<td><code>130.198.76.125</code><br><code>168.1.209.20</code></td>
412-
</tr>
413-
</tbody>
414-
</table></p>
415354
* **{{site.data.keyword.la_full_notm}}**:
416355
<pre class="screen">TCP port 443, port 80 FROM &lt;each_worker_node_public_IP&gt; TO &lt;logDNA_public_IP&gt;</pre>
417356
Replace &gt;<em>logDNA_public_IP&gt;</em> with the [LogDNA IP addresses](/docs/services/Log-Analysis-with-LogDNA?topic=LogDNA-network#network).

‎cs_health.md

+6-40
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2014, 2019
5-
lastupdated: "2019-09-26"
5+
lastupdated: "2019-10-01"
66

77
keywords: kubernetes, iks, logmet, logs, metrics
88

@@ -42,7 +42,7 @@ You can choose your logging solution based on which cluster components you need
4242
<dl>
4343

4444
<dt>{{site.data.keyword.la_full}}</dt>
45-
<dd>Manage pod container logs by deploying LogDNA as a third-party service to your cluster. To use {{site.data.keyword.la_full_notm}}, you must deploy a logging agent to every worker node in your cluster. This agent collects logs with the extension `*.log` and extensionless files that are stored in the `/var/log` directory of your pod from all namespaces, including `kube-system`. The agent then forwards the logs to the {{site.data.keyword.la_full_notm}} service. For more information about the service, see the [{{site.data.keyword.la_full_notm}}](/docs/services/Log-Analysis-with-LogDNA?topic=LogDNA-about) documentation. To get started, see [Managing Kubernetes cluster logs with {{site.data.keyword.loganalysisfull_notm}} with LogDNA](/docs/services/Log-Analysis-with-LogDNA/tutorials?topic=LogDNA-kube#kube).
45+
<dd>Manage pod container logs by deploying LogDNA as a third-party service to your cluster. To use {{site.data.keyword.la_full_notm}}, you must deploy a logging agent to every worker node in your cluster. This agent collects logs with the extension `*.log` and extensionless files that are stored in the `/var/log` directory of your pod from all namespaces, including `kube-system`. The agent then forwards the logs to the {{site.data.keyword.la_full_notm}} service. For more information about the service, see the [{{site.data.keyword.la_full_notm}}](/docs/services/Log-Analysis-with-LogDNA?topic=LogDNA-about) documentation. To get started, see [Managing Kubernetes cluster logs with {{site.data.keyword.la_full_notm}}](/docs/services/Log-Analysis-with-LogDNA/tutorials?topic=LogDNA-kube#kube).
4646

4747
<dt>{{site.data.keyword.at_full}}</dt>
4848
<dd>To monitor user-initiated administrative activity made in your cluster, {{site.data.keyword.containershort_notm}} automatically generates cluster management events and forwards these event logs to {{site.data.keyword.at_full_notm}}. To access these logs, [provision an instance of {{site.data.keyword.at_full_notm}}](/docs/services/Activity-Tracker-with-LogDNA?topic=logdnaat-getting-started). For more information about the types of {{site.data.keyword.containerlong_notm}} events that you can track, see [Activity Tracker events](/docs/containers?topic=containers-at_events).</dd>
@@ -58,14 +58,6 @@ You can choose your logging solution based on which cluster components you need
5858
<dd>If you have special requirements, you can set up your own logging solution. Check out third-party logging services that you can add to your cluster in [Logging and monitoring integrations](/docs/containers?topic=containers-supported_integrations#health_services). To check the logs of an individual Kubernetes pod or other resource, you can run `kubectl logs <resource_name>`. By default, logs are stored in `/var/log` for the namespace. For example, you can collect container logs from the `/var/log/pods/` path. You might write a script to export logs to a persistent storage device that you can use to analyze with your own logging solution.<p class="important">To check the logs for individual app pods, run `kubectl logs <pod name>`. Do not use the Kubernetes dashboard to stream logs for your pods, which might cause a disruption in your access to the Kubernetes dashboard.</p></dd>
5959
</dd>
6060

61-
<dt>Deprecated: Fluentd with {{site.data.keyword.loganalysisfull}}</dt>
62-
<dd><p class="deprecated">Previously, you could create a logging configuration to forward logs that are collected by the Fluentd cluster component to {{site.data.keyword.loganalysisfull_notm}}. As of 30 April 2019, you cannot provision new {{site.data.keyword.loganalysisshort_notm}} instances, and all Lite plan instances are deleted. On 30 September 2019, {{site.data.keyword.containerlong_notm}} is disabling log forwarding from the Fluentd cluster component to {{site.data.keyword.loganalysisshort_notm}} for existing premium plan instances. To continue collecting logs for your cluster, you must set up {{site.data.keyword.la_full_notm}} or change your configuration to forward logs to an external server.</p>
63-
</dd>
64-
65-
<dt>Deprecated: {{site.data.keyword.cloudaccesstrailfull_notm}} with LogAnalysis</dt>
66-
<dd><p class="deprecated">Previously, you could collect and forward audit logs to {{site.data.keyword.cloudaccesstrailfull_notm}} with LogAnalysis. As of 30 April 2019, you cannot provision new {{site.data.keyword.loganalysisshort_notm}} instances, and all Lite plan instances are deleted. Existing premium plan instances are supported until 30 September 2019. To continue collecting audit logs for your cluster, you must set up {{site.data.keyword.at_full_notm}}.</p>
67-
</dd>
68-
6961
</dl>
7062

7163
<br />
@@ -83,7 +75,7 @@ Manage logs by deploying LogDNA as a third-party service to your cluster.
8375
To use {{site.data.keyword.la_full_notm}}, you must deploy a logging agent to every worker node in your cluster.
8476
{: shortdesc}
8577

86-
This agent collects logs with the extension `*.log` and extensionless files that are stored in the `/var/log` directory of your pod from all namespaces, including `kube-system`. The agent then forwards the logs to the {{site.data.keyword.la_full_notm}} service. For more information about the service, see the [{{site.data.keyword.la_full_notm}}](/docs/services/Log-Analysis-with-LogDNA?topic=LogDNA-about) documentation. To get started, see [Managing Kubernetes cluster logs with {{site.data.keyword.loganalysisfull_notm}} with LogDNA](/docs/services/Log-Analysis-with-LogDNA/tutorials?topic=LogDNA-kube#kube).
78+
This agent collects logs with the extension `*.log` and extensionless files that are stored in the `/var/log` directory of your pod from all namespaces, including `kube-system`. The agent then forwards the logs to the {{site.data.keyword.la_full_notm}} service. For more information about the service, see the [{{site.data.keyword.la_full_notm}}](/docs/services/Log-Analysis-with-LogDNA?topic=LogDNA-about) documentation. To get started, see [Managing Kubernetes cluster logs with {{site.data.keyword.la_full_notm}}](/docs/services/Log-Analysis-with-LogDNA/tutorials?topic=LogDNA-kube#kube).
8779

8880
### Forwarding Kubernetes API audit logs
8981
{: #webhook_logdna}
@@ -323,8 +315,7 @@ The following table shows the different options that you have when you configure
323315
</tr>
324316
<tr>
325317
<td><code><em>--hostname</em></code></td>
326-
<td><p>For {{site.data.keyword.loganalysisshort_notm}}, use the [ingestion URL](/docs/services/CloudLogAnalysis?topic=cloudloganalysis-log_ingestion#log_ingestion_urls). If you do not specify an ingestion URL, the endpoint for the region in which you created your cluster is used.</p>
327-
<p>For syslog, specify the hostname or IP address of the log collector service.</p></td>
318+
<td>Specify the hostname or IP address of the log collector service.</td>
328319
</tr>
329320
<tr>
330321
<td><code><em>--port</em></code></td>
@@ -719,31 +710,6 @@ Because Kubernetes API Server logs are automatically streamed, they're also auto
719710
<br />
720711
721712
722-
## Deprecated: Forwarding logs to {{site.data.keyword.loganalysisfull_notm}}
723-
{: #loga}
724-
725-
Previously, you could create a logging configuration to forward logs that are collected by the Fluentd cluster component to {{site.data.keyword.loganalysisfull_notm}}. As of 30 April 2019, {{site.data.keyword.loganalysisfull_notm}} is deprecated. You cannot provision new {{site.data.keyword.loganalysisshort_notm}} instances, and all Lite plan instances are deleted. Existing premium plan instances are supported until 30 September 2019.
726-
{: deprecated}
727-
728-
To continue collecting logs for your cluster, you have the following options:
729-
* Set up {{site.data.keyword.la_full_notm}}. For more information, see [Transitioning to {{site.data.keyword.la_full_notm}}](/docs/services/CloudLogAnalysis?topic=cloudloganalysis-transition).
730-
* [Change your configuration to forward logs to an external server](#configuring).
731-
732-
For more information about existing {{site.data.keyword.loganalysisshort_notm}} instances, see the [{{site.data.keyword.loganalysisshort_notm}} documentation](/docs/services/CloudLogAnalysis?topic=cloudloganalysis-containers_kube_other_logs).
733-
734-
<br />
735-
736-
737-
## Deprecated: Forwarding Kubernetes API audit logs to {{site.data.keyword.cloudaccesstrailfull_notm}} with LogAnalysis
738-
{: #api_forward}
739-
740-
<p class="deprecated">Previously, you could collect and forward audit logs to {{site.data.keyword.cloudaccesstrailfull_notm}} with LogAnalysis. As of 30 April 2019, you cannot provision new {{site.data.keyword.loganalysisshort_notm}} instances, and all Lite plan instances are deleted. Existing premium plan instances are supported until 30 September 2019.</p>
741-
742-
To continue collecting audit logs for your cluster, you must set up {{site.data.keyword.at_full_notm}}. For more information about the types of {{site.data.keyword.containerlong_notm}} events that you can track, see [Activity Tracker events](/docs/containers?topic=containers-at_events). For more information about the service, see the [{{site.data.keyword.at_full_notm}}](/docs/services/Activity-Tracker-with-LogDNA?topic=logdnaat-getting-started) documentation.
743-
744-
<br />
745-
746-
747713
## Choosing a monitoring solution
748714
{: #view_metrics}
749715
@@ -758,8 +724,8 @@ To avoid conflicts when using metrics services, be sure that clusters across res
758724
{: tip}
759725
760726
<dl>
761-
<dt>{{site.data.keyword.mon_full_notm}}</dt>
762-
<dd>Gain operational visibility into the performance and health of your apps by deploying Sysdig as a third-party service to your worker nodes to forward metrics to {{site.data.keyword.monitoringlong}}. For more information, see [Analyzing metrics for an app that is deployed in a Kubernetes cluster](/docs/services/Monitoring-with-Sysdig/tutorials?topic=Sysdig-kubernetes_cluster#kubernetes_cluster).</dd>
727+
<dt>{{site.data.keyword.mon_full}}</dt>
728+
<dd>Gain operational visibility into the performance and health of your apps by deploying Sysdig as a third-party service to your worker nodes to forward metrics to {{site.data.keyword.mon_full_notm}}. For more information, see [Analyzing metrics for an app that is deployed in a Kubernetes cluster](/docs/services/Monitoring-with-Sysdig/tutorials?topic=Sysdig-kubernetes_cluster#kubernetes_cluster).</dd>
763729
764730
<dt>Kubernetes dashboard</dt>
765731
<dd>The Kubernetes dashboard is an administrative web interface where you can review the health of your worker nodes, find Kubernetes resources, deploy containerized apps, and troubleshoot apps with logging and monitoring information. For more information about how to access your Kubernetes dashboard, see [Launching the Kubernetes dashboard for {{site.data.keyword.containerlong_notm}}](/docs/containers?topic=containers-app#cli_dashboard).</dd>

‎cs_integrations_overview.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2014, 2019
5-
lastupdated: "2019-08-23"
5+
lastupdated: "2019-10-01"
66

77
keywords: kubernetes, iks, helm
88

@@ -118,7 +118,7 @@ You can use various external services and catalog services with a standard Kuber
118118
<tr>
119119
<td>{{site.data.keyword.la_full}}</td>
120120
<td>Cluster and app logs</td>
121-
<td>Add log management capabilities to your cluster by deploying LogDNA as a third-party service to your worker nodes to manage logs from your pod containers. For more information, see [Managing Kubernetes cluster logs with {{site.data.keyword.loganalysisfull_notm}} with LogDNA](/docs/services/Log-Analysis-with-LogDNA/tutorials?topic=LogDNA-kube#kube).</td>
121+
<td>Add log management capabilities to your cluster by deploying LogDNA as a third-party service to your worker nodes to manage logs from your pod containers. For more information, see [Managing Kubernetes cluster logs with {{site.data.keyword.la_full_notm}}](/docs/services/Log-Analysis-with-LogDNA/tutorials?topic=LogDNA-kube#kube).</td>
122122
<td><img src="images/confirm.svg" width="32" alt="Feature available" style="width:32px;" /></td>
123123
<td><img src="images/confirm.svg" width="32" alt="Feature available" style="width:32px;" /></td>
124124
</tr>
@@ -304,7 +304,7 @@ You can use various external services and catalog services with a standard Kuber
304304
</tr>
305305
<tr>
306306
<td>{{site.data.keyword.la_full_notm}}</td>
307-
<td>Add log management capabilities to your cluster by deploying LogDNA as a third-party service to your worker nodes to manage logs from your pod containers. For more information, see [Managing Kubernetes cluster logs with {{site.data.keyword.loganalysisfull_notm}} with LogDNA](/docs/services/Log-Analysis-with-LogDNA/tutorials?topic=LogDNA-kube#kube).</td>
307+
<td>Add log management capabilities to your cluster by deploying LogDNA as a third-party service to your worker nodes to manage logs from your pod containers. For more information, see [Managing Kubernetes cluster logs with {{site.data.keyword.la_full_notm}}](/docs/services/Log-Analysis-with-LogDNA/tutorials?topic=LogDNA-kube#kube).</td>
308308
<td><img src="images/confirm.svg" width="32" alt="Feature available" style="width:32px;" /></td>
309309
<td><img src="images/confirm.svg" width="32" alt="Feature available" style="width:32px;" /></td>
310310
</tr>

‎cs_istio.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2014, 2019
5-
lastupdated: "2019-09-25"
5+
lastupdated: "2019-10-01"
66

77
keywords: kubernetes, iks, envoy, sidecar, mesh, bookinfo
88

@@ -452,7 +452,7 @@ Before you begin, [install the `istio` and `istio-extras` managed add-ons](#isti
452452
### Setting up logging with {{site.data.keyword.la_full_notm}}
453453
{: #istio_health_logdna}
454454
455-
Seamlessly manage logs for your app container and the Envoy proxy sidecar container in each pod by deploying LogDNA to your worker nodes to forward logs to {{site.data.keyword.loganalysislong}}.
455+
Seamlessly manage logs for your app container and the Envoy proxy sidecar container in each pod by deploying LogDNA to your worker nodes to forward logs to {{site.data.keyword.la_full}}.
456456
{: shortdesc}
457457
458458
To use [{{site.data.keyword.la_full_notm}}](/docs/services/Log-Analysis-with-LogDNA?topic=LogDNA-about), you deploy a logging agent to every worker node in your cluster. This agent collects logs with the extension `*.log` and extensionless files that are stored in the `/var/log` directory of your pod from all namespaces, including `kube-system`. These logs include logs from your app container and the Envoy proxy sidecar container in each pod. The agent then forwards the logs to the {{site.data.keyword.la_full_notm}} service.

0 commit comments

Comments
 (0)