Skip to content

Latest commit

 

History

History
119 lines (75 loc) · 5 KB

cs_istio_health.md

File metadata and controls

119 lines (75 loc) · 5 KB
copyright lastupdated keywords subcollection
years
2014, 2023
2023-01-30
kubernetes, mesh, Prometheus, Grafana, Jaeger, Kiali, controlz, envoy
containers

{{site.data.keyword.attribute-definition-list}}

Observing Istio traffic

{: #istio-health}

Log and monitor your apps that are managed by Istio on {{site.data.keyword.containerlong_notm}}. {: shortdesc}

Setting up logging with {{site.data.keyword.la_full_notm}}

{: #istio_health_la}

Seamlessly manage logs for your app container and the Envoy proxy sidecar container in each pod by deploying {{site.data.keyword.la_short}} agents to your worker nodes to forward logs to {{site.data.keyword.la_full}}. {: shortdesc}

To use {{site.data.keyword.la_full_notm}}, 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.

To get started, set up logging for your cluster by following the steps in Managing Kubernetes cluster logs with {{site.data.keyword.la_full_notm}}.

Setting up monitoring with {{site.data.keyword.mon_full_notm}}

{: #istio_health_mon}

Gain operational visibility into the performance and health of your Istio-managed apps by deploying a {{site.data.keyword.mon_short}} agent to your worker nodes to forward metrics to {{site.data.keyword.mon_full}}. {: shortdesc}

To deploy monitoring agents to your cluster, complete the following steps.

  1. Provision an instance of {{site.data.keyword.mon_full_notm}}{: external}.

  2. Configure a monitoring agent in your cluster.

  3. In the Monitoring console{: external}, click Open Dashboard for the instance that you provisioned.

  4. In the {{site.data.keyword.mon_short}} UI, click Add new dashboard.

  5. Search for Istio and select one of {{site.data.keyword.mon_short}}'s predefined Istio dashboards.

For more information about referencing metrics and dashboards, monitoring Istio internal components, and monitoring Istio A/B deployments and canary deployments, check out the How to monitor Istio, the Kubernetes service mesh{: external} blog post.

Launching the ControlZ component inspection and Envoy sidecar dashboards

{: #istio_inspect}

To inspect specific components of Istio, launch the ControlZ{: external} and Envoy{: external} dashboards. {: shortdesc}

The ControlZ dashboard accesses the Istio component ports to provide an interactive view into the internal state of each component. The Envoy dashboard provides configuration information and metrics for an Envoy sidecar proxy that runs in an app pod.

Before you begin

ControlZ

{: #controlz}

  1. Get the pod name for the Istio component that you want to inspect. You can inspect the component pods for istio-citadel, istio-galley, istio-pilot, istio-policy, and istio-telemetry.

    kubectl get pods -n istio-system | grep istio

    {: pre}

    Example output

    NAME                                      READY   STATUS    RESTARTS   AGE
istio-citadel-869c7f9498-wtldz            1/1     Running   0          2m
istio-egressgateway-69bb5d4585-qxxbp      1/1     Running   0          2m
istio-galley-75d7b5bdb9-c9d9n             1/1     Running   0          2m
istio-ingressgateway-5c8764db74-gh8xg     1/1     Running   0          2m
istio-pilot-55fd7d886f-vv6fb              2/2     Running   0          2m
istio-policy-6bb6f6ddb9-s4c8t             2/2     Running   0          2m
istio-sidecar-injector-7d9845dbb7-r8nq5   1/1     Running   0          2m
istio-telemetry-7695b4c4d4-tlvn8          2/2     Running   0          2m
istio-tracing-55bbf55878-z4rd2            1/1     Running   0          2m

    {: screen}

  2. Access the ControlZ dashboard for that component.

    istioctl dashboard controlz <component_pod_name>.istio-system

    {: pre}

Envoy

{: #envoy}

  1. Get the name of the app pod where you want to inspect the Envoy sidecar container.

    kubectl get pods -n <namespace>

    {: pre}

  2. Access the Envoy dashboard for that pod.

    istioctl dashboard envoy <pod-name>.<namespace>

    {: pre}