Other Settings¶
Contains 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 kept in real-time sync with the user'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 reflect account permissions. Suitable for personal scripts or third-party platform integrations.
-
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, please do not disclose it).
- Supports "Regenerate".
- Supports generating a "Temporary Authorization Code", used to temporarily exchange for an API Key during automatic installation of Owl CLI or AI tools. Valid for 30 minutes after generation and becomes invalid immediately after use.
System Notices¶
After subscribing to system notices, 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 grow continuously. It is recommended that you promptly check the query conditions and grouping settings. If the system limit of {alert cache limit} is reached, the monitor will be automatically paused.
2. Monitor Auto-paused (Cache Limit Exceeded)
Once the number of detection objects cached by a monitor reaches the system limit of {100,000}, the system will automatically pause this monitor and send an email notification. During the pause, the monitor will stop running. To prevent the continuous generation of excessive detection objects from 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 Blocked)
Once the system detects that a monitor's detection object grouping fields pose a high-cardinality risk (e.g., values in the field exhibit characteristics exceeding 32 characters in length), it will automatically pause this monitor and send an email notification. Such fields often generate a large number of discrete groups, leading to rapid growth in the number of detection objects. Please adjust the monitor's query and try again.
Go to Monitoring > Notification Targets, and you can directly click "Subscribe to System Notices" to check if there are any delivery failures or if a notification target has been disabled by the system.
Or, go to the Create/Edit page for a notification target and click "Subscribe to System Notices".
Go to Management > Cloud Accounts, and directly click "Subscribe to System Notices" to check if the cloud account configuration status is valid.
If the 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 notice is triggered, you can view all notice events in the notice list and manage them through the following operations:
- Filter notice types by scenario.
- Filter based on the notice's title or content.
- View unread only.
- Mark all as read.