Monitor
💡 Tip: This feature is only supported in V4.1.2 and later versions
The monitoring entry point is as shown below:
Statistics
Agent Monitoring
The Data Center provides comprehensive statistics and analysis of intelligent assistant usage and user dialogue content, helping users better understand AI usage effectiveness and operational status, optimizing management and decision-making.
The Data Center supports data statistics from assistant dimension, system API dimension, time dimension.
Agents Analytics
This section focuses on quantitative analysis of the usage of each AI assistant, including:
- Number of Users: The number of unique users who have interacted with the assistant.
- Conversation Count: The total number of interactions between users and the assistant, measuring usage activity.
- Token Consumption: Measures the resource consumption of model calls during assistant operation.
- Assistant Usage Ranking: Ranks all assistants according to usage frequency, identifying high-frequency use assistants.
- Token Consumption Ranking: Statistics on token usage of each assistant, assisting resource optimization and cost control.
Conversation Analytics
This section delves into the content of dialogues between users and assistants, gaining insights into user needs and interaction patterns, including:
- High-frequency words: Extracts keywords from user dialogues, identifying focus hotspots and demand trends.
- Conversation Logs: View historical dialogue details, used for quality review, issue investigation, and content auditing.
💡 Tip: Dialogue interaction statistics and assistant usage ranking are updated once a day; other information like dialogue logs is updated in real-time.
Notification
Notification Management is used to count and view various notification messages received by all users in the system. Through this function, administrators can track the delivery of notifications, understand whether users have read them, and whether the notification content has been effectively communicated.
For example: When a user uses an intelligent agent for dialogue and performs a feedback operation on the agent's answer, the system sends a feedback notification to that user. Such notifications are recorded and displayed in Notification Management.
Function Description
On the Notification Management page, the following information can be viewed:
- Recipient: The user account or username that received the notification.
- Notification Status: Whether the current notification has been read (Read / Unread).
- Sending Time: The specific time the system sent the notification.
- Notification Content: Detailed information of the notification, supporting viewing of original prompts, feedback results, etc.
- Notification Category: The category to which the notification belongs, such as feedback notification, system notification, task reminder, etc.
💡 Tip: Supports filtering notifications by time dimension.
System Logs
This system provides comprehensive log recording and analysis functions, covering three core logs: operation, event, and login, helping you achieve system behavior tracking, security auditing, and anomaly investigation.
💡 Tip: The search range for logs has been increased to 1 year, facilitating users to perform auditing and analysis over longer time spans.
Operation Logs
- Operation logs are used to record all key operational behaviors of users in the system, helping administrators track resource change history, audit system usage, and investigate potential problems.
- The system automatically captures each operation of resource creation, update, publication, or deletion, ensuring traceability and security of operations.
- To further enhance the auditability of knowledge base management, operation logs have been enhanced to record knowledge base-related resources, including Workspace (work space), File (file), QnA (Q&A pairs) operations.
Field Description
| Field Name | Description |
|---|---|
| User | The user account name that performed the operation |
| Operation Time | The specific timestamp when the operation occurred, used for auditing and time sorting |
| Resource Type | The resource classification of the operated object, such as knowledge base, data, AIStudio |
| Subresource Type | The sub-resource involved in the operation, such as QnA, personal/enterprise space, personal/organization agent |
| Operation Type | Represents the source type of the operation, such as Update, Publish, UPLOAD, CONFIG_INDEX, RESEGMENT |
| Result | Represents the result of this operation, Success or Failed |
| IP | The IP address of the user when performing the operation |
| Device | The device type, browser used by the user. |
| Content | Detailed operation content, in JSON format, containing request and response information |
Event Logs
Event logs are used to record various important events generated during the internal operation of the system, such as scheduled task execution, status changes, error alarms, etc. They are an important tool for monitoring system health and investigating internal problems.
Field Description
| Field Name | Field Function |
|---|---|
| ID | A unique identifier automatically generated by the system, used to distinguish each event record |
| Name | Briefly describes the event content, facilitating quick understanding of the event nature |
| Time | Records the specific timestamp when the event occurred, used for time sorting and analysis |
| Type | Identifies the event category (security, system, application), supports classification filtering |
| Trigger Type | Records whether the event trigger type is system or api |
| Description | Detailed operation content, in JSON format |
Login Logs
Login logs comprehensively record all user authentication behaviors and are the basis for security auditing and identifying abnormal logins.
Field Description
| Field Name | Field Function |
|---|---|
| Username | Records the user account name that attempted login, supports user behavior analysis |
| Time | Records the specific time when the login occurred, used for time series analysis |
| IP Address | Records the network address of the login source, supports geographical location analysis and anomaly detection |
| Login Method | Identifies the login authentication method (password, single sign-on, etc.), supports security policy analysis |
Bill Details
In the SERVICEME system, you can view the billing details of token usage. The line chart at the top of the interface shows the changes in token-related values at different time points, providing an intuitive display of usage trends. The table below details the token consumption of various models and the corresponding costs during specific periods, listing associated usage types and other information, making it easy to clearly understand the billing situation of each token usage.
Information Provided on the Billing Details Page
The Billing Details interface allows you to view the following information:
- Model Group: Displays the group category to which the model belongs.
- Model Set: Indicates the set name to which this model belongs.
- Model: Displays the specific model name used.
- Channel: Identifies the channel through which the model runs.
- API Key Name: Presents the name of the API key used to access the model.
- Input Token: Records the number of tokens input to the model.
- Input token (Cache Hit): Displays the number of input tokens when a cache hit occurs.
- Output token: Shows the number of tokens consumed by the model output.
- Time: Records the specific time when the model operation occurred.
- Operation: Provides executable operation options such as viewing log details.
Role of Billing Details
- Cost Transparency: Precisely tracks the cost generated by each model call, achieving cost visibility, manageability, and controllability.
- Usage Trend Analysis: Identifies resource consumption patterns through trend charts, providing data support for resource procurement and budget planning.
- Issue Investigation and Optimization: Analyzes the causes of high-cost requests in conjunction with detailed logs, thereby optimizing prompts or business processes to control costs.
- Multi-Dimensional Allocation: Supports allocating costs to different projects or departments through dimensions such as model, channel, and API Key.