Skip to content

Other Settings

Includes various scenario operation configurations at the personal account level.

Workspace Management

For more details, refer to Manage Workspace.

Personal API Key

A Personal API Key is an access credential bound to a user account. Its permissions are always synchronized with the account's full functional permissions on the platform (including dashboards, data queries, etc.). It is used with OWL and MCP Server.

Difference from Workspace-level API Key

  • Personal API Key: Bound to a personal account, permissions automatically take effect with the account's permissions, suitable for personal scripts or third-party platform integration.

  • Workspace-level API Key: Bound to a workspace role, permissions must be manually specified during creation, primarily used for service-to-service communication like DataKit reporting.

Click to open the window to copy your Personal API Key (❗️This key represents your personal identity, do not disclose it).

Supports "Regenerate".

System Notifications

After subscribing to system notifications, the system will trigger events in the following key scenarios and send notifications to the subscriber's email:

Once a data forwarding rule becomes invalid, the system will send an email notification.

1. Alert Count Approaching Limit Reminder

Once the number of detection objects monitored by a monitor reaches {80%} of the system limit, the system will send an email notification (maximum once per day). This monitor may be using high-cardinality fields for aggregation, causing the number of detection objects to continuously increase. It is recommended that you promptly check the query conditions and grouping settings. If the system limit {alert cache limit} is reached, the monitor will be automatically paused.

2. Monitor Auto-paused (Cache Exceeded Limit)

Once the number of cached detection objects for a monitor reaches the system limit {100,000}, the system will automatically pause the monitor and send an email notification. The monitor will stop running during the pause. To avoid continuously generating too many detection objects affecting system stability, please check and adjust the query conditions and grouping settings. You can also modify and re-save the monitor to resume its operation immediately.

3. Monitor Auto-paused (High-cardinality Field Interception)

Once the system detects that a monitor's detection object grouping field has a high-cardinality risk (e.g., field values with characteristics exceeding 32 characters in length), it will automatically pause the monitor and send an email notification. Such fields typically generate a large number of discrete groups, causing the number of detection objects to grow rapidly. Please adjust the monitor's query and try again.

Go to Monitoring > Notification Targets, and you can directly click "Subscribe to System Notifications" to learn if a notification target has failed to send or has been disabled by the system.

Or go to the create/edit page of a notification target and click "Subscribe to System Notifications".

Go to Management > Cloud Accounts, and directly click "Subscribe to System Notifications" to learn if the cloud account configuration status is valid.

If a workspace's data reporting triggers the configured limit, the system will send an email notification.

After clicking the "Subscribe" button above, the system will automatically send relevant notification emails to your mailbox when new messages are available.

After a system notification is triggered, you can view all notification events in the notification list and manage them with the following operations:

  • Filter notification types by scenario type.
  • Filter based on the notification's title or content.
  • Show only unread.
  • Mark all as read.