Observability API 總覽

Observability API 使用 Kubernetes 自訂資源，並依賴 Kubernetes 資源模型 (KRM) 來佈建及管理記錄和監控資源。

您可以使用 Observability API，管理特定機構或自訂專案中 Observability 服務的生命週期。可觀測性服務的生命週期包括安裝、升級和解除安裝等作業。您必須根據要管理的 Observability 服務，將自訂資源部署至專案。

系統會自動為已佈建的專案提供許多可觀測性服務，例如記錄、監控和快訊。

服務端點

下列網址是 Observability KRM API 的 API 端點：

• 記錄群組：

  https://MANAGEMENT_API_SERVER_ENDPOINT/apis/logging.gdc.goog/v1
  

• 監控群組：

  https://MANAGEMENT_API_SERVER_ENDPOINT/apis/monitoring.gdc.goog/v1
  

• 可觀測性群組：

  https://MANAGEMENT_API_SERVER_ENDPOINT/apis/observability.gdc.goog/v1
  

將 MANAGEMENT_API_SERVER_ENDPOINT 替換成 Management API 伺服器的端點。

探索文件

使用 kubectl proxy --port=8001 指令在本機開啟 API 伺服器的 Proxy。然後透過下列任一網址存取探索文件：

• http://127.0.0.1:8001/apis/logging.gdc.goog/v1
• http://127.0.0.1:8001/apis/monitoring.gdc.goog/v1
• http://127.0.0.1:8001/apis/observability.gdc.goog/v1

範例資源

本節包含使用可觀測性 KRM API 的資源範例。

記錄群組

以下是 LoggingTarget 自訂資源的範例，可從 project-1 專案中的特定服務收集記錄：

# Configures a log scraping job
apiVersion: logging.gdc.goog/v1
kind: LoggingTarget
metadata:
  # Choose a namespace that matches the namespace of the workload pods
  namespace: project-1
  name: my-service-logging-target
spec:
  # Choose a matching pattern that identifies the pods for this job
  # Optional
  # Relationship between different selectors: 'AND'
  selector:
    # The clusters to collect logs from.
    # The default configuration is to collect logs from all clusters.
    # The relationship between different clusters is an 'OR' relationship.
    # For example, the value '["admin", "system"]' indicates to consider
    # the admin cluster 'OR' the system cluster.
    # Optional
    matchClusters:
    - cluster-1
    - cluster-2

    # The pod name prefixes to collect logs from.
    # The Observability platform scrapes all pods with names
    # that start with the specified prefixes.
    # The values must contain '[a-z0-9-]' characters only.
    # The relationship between different list elements is an 'OR' relationship.
    # Optional
    matchPodNames:
      - pod-1
      - pod-2

    # The container name prefixes to collect logs from.
    # The Observability platform scrapes all containers with names
    # that start with the specified prefixes.
    # The values must contain '[a-z0-9-]' characters only.
    # The relationship between different list elements is an 'OR' relationship.
    # Optional
    matchContainerNames:
      - container-1
      - container-2

  # Choose the predefined parser for log entries.
  # Use parsers to map the log output to labels and extract fields.
  # Specify the log format.
  # Optional
  # Options: klog_text, klog_json, klogr, gdch_json, json
  parser: klog_text

  # Specify an access level for log entries.
  # The default value is 'ao'.
  # Optional
  # Options: ao, pa, io
  logAccessLevel: ao

  # Specify a service name to be applied as a label
  # For user workloads consider this field as a workload name
  # Required
  serviceName: service-name

  # The additional static fields to apply to log entries.
  # The field is a key-value pair, where the field name is the key and
  # the field value is the value.
  # Optional
  additionalFields:
    app: workload2
    key: value

監控群組

以下是 MonitoringTarget 自訂資源的範例，可從 project-1 專案中的工作負載收集指標：

apiVersion: monitoring.gdc.goog/v1
kind: MonitoringTarget
metadata:
  # Choose the same namespace as the workload pods
  namespace: project-1
  name: string
spec:
  # Choose matching pattern that identifies pods for this job
  # Optional
  # Relationship between different selectors: AND
  selector:
    # Choose clusters to consider for this job
    # Optional
    # List
    # Default: All clusters applicable to this project.
    # Relationship between different list elements: OR
    matchClusters:
      - string

    # Choose pod-labels to consider for this job
    # Optional: Map of key-value pairs.
    # Default: No filtering by label.
    # Relationship between different pairs: AND
    matchLabels:
      key1: value1

    # Choose annotations to consider for this job
    # Optional: Map of key-value pairs
    # Default: No filtering by annotation
    # Relationship between different pairs: AND
    matchAnnotations:
      key1: value1

  # Configure the endpoint exposed for this job
  podMetricsEndpoints:
    # Choose port either via static value or annotation
    # Optional
    # Annotation takes priority
    # Default: static port 80
    port:
      value: integer
      annotation: string

    # Choose path either via static value or annotation
    # Optional
    # Annotation takes priority
    # Default: static path /metrics
    path:
      value: string
      annotation: string

    # Choose scheme either via static value (http or https) or annotation
    # Optional
    # Annotation takes priority
    # Default: static scheme http
    scheme:
      value: string
      annotation: string

    # Choose the frequency to scrape the metrics endpoint defined in podMetricsEndpoints
    # Optional
    # Default: 60s
    scrapeInterval: string

    # Dynamically rewrite the label set of a target before it gets scraped.
    # https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config
    # Optional
    # Default: No filtering by label
    metricsRelabelings:
      - sourceLabels:
          - string
        separator: string
        regex: string
        action: string
        targetLabel: string
        replacement: string

可觀測群組

以下是 ObservabilityPipeline 自訂資源的範例，可更新 platform-obs 專案命名空間中資訊主頁的儲存空間大小：

# Configure observability pipeline
apiVersion: observability.gdc.goog/v1
kind: ObservabilityPipeline
metadata:
  # Don't change the namespace or name.
  namespace: platform-obs
  name: observability-config
spec:
  ...
  monitoring:
    grafana:
      storageSize: 1Gi # Configure the new storage size for dashboards in the project.
    ...