< 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. Log Collection / 
  7. Enable Log Collection

Documentation

Last updated:
    Edit

    Enable Log Collection

    This section introduces how to modify the configuration of the "WhizardTelemetry Logging" extension to enable the log collection feature.

    Note

    After enabling, the Log Collection option will be displayed under the Project Settings menu in the left navigation pane.

    Prerequisites

    • You should have the platform-admin role on the KubeSphere platform. For more information, see Users and Platform Roles.

    • WhizardTelemetry Logging should have been installed and enabled.

    Steps

    1. Log in to the KubeSphere web console with a user who has the platform-admin role.

    2. Click Extensions Center.

    3. Click the installed WhizardTelemetry Logging extension to enter the details page.

    4. Click more under the icon, and select Extension Config.

    5. In the extension configuration file, set the logsidecar-injector.enabled parameter to true, then save the file.

      logsidecar-injector:
  enabled: true
      Note

      Since the job that updates this parameter only runs on the host cluster, setting logsidecar-injector.enabled in member clusters will not take effect if you only want to enable or disable the log collection feature for certain member clusters. Each time you modify this parameter, you need to modify the parameter in the host cluster at the same time to trigger the parameter update.

      For example, when you need to turn off the log collection feature of a certain member cluster, just set logsidecar-injector.enabled: false in the configuration of that member cluster, and then add logsidecar-injector.updateVersion: 1 in the configuration of the host cluster. For subsequent operations, you only need to update logsidecar-injector.updateVersion to trigger the update.

    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 : Use the Container Log Query Tool
    What’s on this Page