< 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. Notification History / 
  7. View Notification History

Documentation

Last updated:
    Edit

    View Notification History

    This section describes how to view notification history.

    Prerequisites

    • You should have the Platform Settings Management permission on the KubeSphere platform. For more information, refer to "Platform Roles".

    • WhizardTelemetry Notification should have been installed and enabled.

    Steps

    1. Log in to the KubeSphere web console with a user who has the Platform Settings Management permission.

    2. Click cogwheel in the upper-right corner of the KubeSphere web console to enter the Platform Settings page.

    3. Click Notification Management > Notification History in the left navigation pane.

      • The Notification History page provides the following information:

        ParameterDescription

        Alert Name

        The name of the alert sent as a notification to users.

        Alert Type

        The type of system event indicated by the alert.

        • Metric Alert: Resource metrics meet the alert trigger conditions.

        • Audit Alert: System audit events, such as API calls.

        • Event Alert: System resource events, such as resource creation, deletion, modification, etc.

        Alert Severity

        The level of the alert, including Info, Warning, Error, Critical.

        Message

        The content of the alert message.

        Status

        The status of the alert: Firing/Resolved.

        Firing: A triggered alert will generate a firing notification.

        Resolved: After a period of time (default 5 minutes), if no further alerts are received, the status will change to resolved.

        Project

        The project where the resource triggering the alert is located.

        Service

        The service triggering the alert.

        Pod

        The pod triggering the alert.

        Container

        The container triggering the alert.

        Notification Time

        The time the notification was sent.

      • Select a cluster from the dropdown list at the top left of the list to view the notification history in a specific cluster.

      • Click the search box above the list to search for notification history records by alert name, alert severity, message, status, project, and time range.

      • Click refresh in the upper right corner of the list to refresh the list information.

      • Click cogwheel in the upper right corner of the list to customize the information displayed in the list.

    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 : Modify Notification Language
    What’s on this Page