Alauda Service Mesh v2 Docs
  • English

    • Metrics and Service Mesh

    TOC

    Using metricsConfiguring Monitoring with Service Mesh

    Using metrics

    A monitoring plugin, ACP Basic Monitoring (previously ACP Monitoring for Prometheus) or ACP Advanced Monitoring (previously ACP Monitoring for VictoriaMetrics), should be installed to provide metrics for the Alauda Service Mesh v2 Operator and Istio control plane.

    When you have added your application to the mesh, you can monitor the in-cluster health and performance of your applications running on Alauda Container Platform with metrics and customized alerts for CPU and memory usage, network connectivity, and other resource usage.

    Configuring Monitoring with Service Mesh

    You can integrate Alauda Service Mesh with monitoring to enable observability in your service mesh. Monitoring provides access to essential built-in tools and supplies the metrics that Kiali, the dedicated console for Istio, uses for its graph, health, and metrics views. Kiali can run without these metrics, but those views are then unavailable.

    Prerequisites

    • Alauda Service Mesh is installed.

    Procedure

    Create a YAML file named servicemonitor.yaml to monitor the Istio control plane:

    Example ServiceMonitor object

    servicemonitor.yaml
    apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: istiod-monitor
  namespace: istio-system
  labels:
    # prometheus=kube-prometheus is required in ACP prometheus.
    prometheus: kube-prometheus
spec:
  targetLabels:
  - app
  selector:
    matchLabels:
      istio: pilot
    matchExpressions:
    - key: istio.io/tag
      operator: DoesNotExist
  endpoints:
  - port: http-monitoring
    interval: 60s
    1. Excludes the services that an IstioRevisionTag creates. They select the same istiod pods as the service of the revision, and selecting both scrapes the control plane twice.

    Apply the YAML file by running the following command:

    kubectl apply -f servicemonitor.yaml

    Create a YAML file named podmonitor.yaml to collect metrics from the Istio proxies (workloads):

    Example PodMonitor object

    podmonitor.yaml
    apiVersion: monitoring.coreos.com/v1
kind: PodMonitor
metadata:
  name: istio-proxies-monitor
  namespace: istio-system
  labels:
    # prometheus=kube-prometheus is required in ACP prometheus.
    prometheus: kube-prometheus
spec:
  selector:
    matchExpressions:
    - key: istio-prometheus-ignore
      operator: DoesNotExist
  namespaceSelector:
    any: true
  jobLabel: envoy-stats
  podMetricsEndpoints:
  - path: /stats/prometheus
    interval: 60s
    relabelings:
    - action: keep
      sourceLabels: [ __meta_kubernetes_pod_container_name ]
      regex: "istio-proxy"
    - action: keep
      sourceLabels: [__meta_kubernetes_pod_annotationpresent_prometheus_io_scrape]
    - sourceLabels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]
      action: replace
      regex: ([^:]+)(?::\d+)?;(\d+)
      replacement: "$1:$2"
      targetLabel: __address__
    - sourceLabels: [__meta_kubernetes_pod_label_app_kubernetes_io_name, __meta_kubernetes_pod_label_app]
      separator: ";"
      targetLabel: "app"
      action: replace
      regex: "(.+);.*|.*;(.+)"
      replacement: "${1}${2}"
    - sourceLabels: [__meta_kubernetes_pod_label_app_kubernetes_io_version, __meta_kubernetes_pod_label_version]
      separator: ";"
      targetLabel: "version"
      action: replace
      regex: "(.+);.*|.*;(.+)"
      replacement: "${1}${2}"
    # additional labels
    - sourceLabels: [__meta_kubernetes_namespace]
      action: replace
      targetLabel: namespace
    # - action: replace
    #   targetLabel: mesh_id
    #   replacement: "<mesh_id>"
    1. Create the PodMonitor object once, in the Istio control plane namespace. namespaceSelector with any: true makes it scrape the proxies of every namespace, and a copy in another namespace scrapes all of them a second time.
    2. Specify the actual mesh ID. A mesh_id label is only necessary when running in ambient mode and multiple clusters share the same monitoring data source.

    Apply the YAML file by running the following command:

    kubectl apply -f podmonitor.yaml

    Create a YAML file named asm-telemetry.yaml to configure prometheus metrics to istio proxies (workloads):

    Example Istio Telemetry resource

    asm-telemetry.yaml
    apiVersion: telemetry.istio.io/v1
kind: Telemetry
metadata:
  name: asm-default
  namespace: istio-system
spec:
  metrics:
    - providers:
        - name: prometheus
      overrides:
        - tagOverrides:
            mesh_id:
              value: xds.node.metadata['MESH_ID']
    1. Add mesh_id label to prometheus metrics.

    Apply the YAML file by running the following command:

    kubectl apply -f asm-telemetry.yaml