< img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3131724&fmt=gif" />
🚀 KubeSphere v4.1.2 with Enhancements and Bug Fixes is available now. Read the release notes for v4.1.2 → close
  • English
    • English
    • 简体中文
    1. 1.Create a KubeSphere Cloud account and log in to the platform.
    2. 2.In the upper-right corner, click Console, and then click Lite Cluster on the left.
    3. 3.Create a K8s cluster with KubeSphere installed.
    4. 4.Access KubeSphere with the default account and password (admin/P@88w0rd).
  •  Star
  1. Docs / 
  2. Documentation / 
  3. Extension User Guide / 
  4. WhizardTelemetry Observability Platform / 
  5. WhizardTelemetry Logging / 
  6. Configure Log Management

Documentation

Last updated:
    Edit

    Configure Log Management

    WhizardTelemetry Logging supports configuring extensions to collect specified logs and create log indices by project.

    Note

    For more configuration information, see the details page of the "WhizardTelemetry Logging" extension in the Extensions Center.

    Collect Specified Logs

    WhizardTelemetry Logging supports setting filter conditions to collect logs that include or exclude specified namespaces, which can reduce the number of logs.

    Edit the following parameters in the configuration of the WhizardTelemetry Logging extension:

    vector-logging:
  filter:
    extraLabelSelector: "app.kubernetes.io/name!=kube-events-exporter"
    extraNamespaceLabelSelector: ""
    # When includeNamespaces and excludeNamespaces are set at the same time, only excludeNamespaces will take effect.
    includeNamespaces: []
    excludeNamespaces: []

    • extraLabelSelector: Only collect logs from pods with this label.

    • extraNamespaceLabelSelector: Only collect logs from pods in namespaces with this label.

    • includeNamespaces: Only collect logs from pods in the specified namespaces.

    • excludeNamespaces: Do not collect logs from pods in the specified namespaces.

    Create Log Indices by Namespace

    WhizardTelemetry Logging supports creating an index for each project (namespace), which can determine the log space occupied by a namespace, facilitate business rectification, and facilitate log analysis.

    Prerequisites

    Version requirements: WhizardTelemetry Logging >= 1.2.0, WhizardTelemetry Platform Service >= 1.1.0.

    Steps

    1. Modify the configuration of the WhizardTelemetry Logging extension. No need to modify the parameters in prefix.

      vector-logging:
  sinks:
    opensearch:
      index:
        prefix: "{{ .cluster }}-{{ .kubernetes.namespace_name }}-logs"
        timestring: "%Y.%m.%d"

    2. Modify the configuration of the WhizardTelemetry Platform Service extension. No need to modify the parameters in indexPrefix.

      whizard-telemetry:
  config:
    logging:
      enable: true
      servers:
        - elasticsearch:
            endpoints:
              - https://opensearch-cluster-data.kubesphere-logging-system:9200
            indexPrefix: "{{ .cluster }}-{{ .kubernetes.namespace_name }}-logs"
            timestring: "%Y.%m.%d"

    Receive the latest news, articles and updates from KubeSphere


    Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.

    Previous : Overview
    What’s on this Page