< 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 Notification / 
  6. User Notification Settings / 
  7. Set Up WeCom Notification

Documentation

Last updated:
    Edit

    Set Up WeCom Notification

    This section describes how to set up WeCom notification. After configuration, you can receive notification messages through WeCom chats or chatbots.

    Prerequisites

    • WhizardTelemetry Notification should have been installed and enabled.

    • You should get the access parameters for the WeCom application in advance. For more information, see WeCom Developer Documentation.

    Steps

    1. Log in to the KubeSphere web console.

    2. Click the current username in the upper-right corner of the page, and then select Notification Settings from the dropdown list.

    3. On the Notification Settings page, under the WeCom tab, set the WeCom notification parameters, and then click OK.

      • Chat Settings > Recipient Settings

        Set the User ID, Department ID, or Tag ID that will receive notifications. Click Add to set multiple IDs.

      • Chatbot Settings > Chatbot Settings

        Webhook URL: The webhook address of the WeCom group bot.

      • Chatbot Settings > Recipient Settings

        Set the User ID or user phone number that will receive notifications. Click Add to set multiple IDs and phone numbers.

      • Filter Conditions

        The notifications sent by KubeSphere are presented in the form of key-value pairs. When the key and value filled in here match the key and value in the label settings of the alert rules in rule groups, the notifications can be filtered by labels and alert notifications that meet specific label conditions can be sent to receivers. Click Add to set multiple conditions.

        ParameterDescription

        Key

        The key in the notification content. Click the dropdown list to select a preset key, or input a custom key in the dropdown list.

        Operator

        The operator for the filter condition.

        • Contains: The value corresponding to the key contains a specific string.

        • Does Not Contain: The value corresponding to the key does not contain a specific string.

        • Exists: The specific key exists in the notification content.

        • Does Not Exist: The specific key does not exist in the notification content.

        • Regex Match: Filter notifications that meet the conditions through a regular expression.

        Values

        The value corresponding to the key must include the specified string. Press Enter to set multiple strings. If the value corresponding to the key contains any of these strings, the condition is met.

      • Click Send Test Message to confirm that the notification channel is working properly.

    4. Click the Notification Disabled switch above to enable WeCom notifications.

    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 : Set Up DingTalk Notification
    What’s on this Page