Skip to main content

Monitoring

The entry point for monitoring is shown below:

Intelligent Agent Monitoring​

The data center provides comprehensive statistics and analysis on the usage of intelligent assistants and user conversation content, helping users better understand the effectiveness and operational status of AI, optimizing management and decision-making.

The data center supports data statistics from the assistant dimension, system API dimension, and time dimension.

Assistant Analysis​

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.
  • Number of Conversations: 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: Sorts all assistants by usage frequency to identify high-frequency assistants.
  • Token Consumption Ranking: Statistics on Token usage by each assistant to assist resource optimization and cost control.

Conversation Analysis​

This section delves into the conversation content between users and assistants, gaining insights into user needs and interaction patterns, including:

  • High-frequency Word Analysis: Extracts keywords from user conversations to identify focus points and demand trends.
  • Conversation Logs: View historical conversation details for quality review, issue troubleshooting, and content auditing.

💡 Tip: Conversation count statistics and assistant usage rankings are updated once daily; conversation logs and other information are updated in real time.

Notification Management​

Notification management is used to count and view all types of notification messages received by users in the system. Through this feature, administrators can track the delivery status of notifications, understand whether users have read them, and whether the notification content has been effectively conveyed.

For example: when a user interacts with an intelligent agent and provides feedback on the agent’s response, the system will send a feedback notification to that user, which will be recorded and displayed in notification management.

Feature Description​

On the notification management page, the following information can be viewed:

  • Recipient: The user account or username who received the notification
  • Notification Status: Whether the notification has been read (Read / Unread)
  • Send 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

Billing Details​

In the SERVICEME system, you can view billing details for Token usage. The line chart at the top of the interface displays the changes in Token-related values at different time points, providing an intuitive presentation of usage trends. The table below records in detail the Token consumption and corresponding costs of various models within a specific time period, and lists related usage types and other information, facilitating a clear understanding of the billing situation for each Token usage.

Information Provided on the Billing Details Page​

The billing details interface allows viewing of the following information:

  • Model Group: Displays the group category to which the model belongs.
  • Model Set: Indicates the collection name to which the model belongs.
  • Model: Shows the specific model name used.
  • Channel: Identifies the channel through which the model is run.
  • API Key Name: Displays the name of the API key used to access the model.
  • Input Token: Records the number of Tokens input into the model.
  • Input Token (Cache Hit): Shows the number of Tokens input when a cache hit occurs.
  • Output Token: Displays the number of Tokens consumed by the model output.
  • Token Cost: Lists the cost generated by Token usage.
  • Time: Records the specific time when the model operation occurred.
  • Operation: Provides executable options such as viewing log details.

Purpose of Billing Details​

  • Real-time Monitoring of Token Consumption: Through billing details, administrators can view the Token consumption of models in real time and judge usage trends based on the line chart.
  • Cost Tracking: Facilitates tracking the cost of each operation, helping administrators control expenses.
  • Log Viewing: Through the view log details function provided in the operation column, users can gain in-depth understanding of each model operation’s specific content, assisting in troubleshooting.

Operation Logs​

💡 Tip: This feature is only supported in version V4.1 and above

Operation logs are used to record all key user operations in the system, helping administrators track resource change history, audit system usage, and troubleshoot potential issues.
The system automatically captures every resource creation, update, publication, or deletion operation to ensure traceability and security of operations.

Field Description​

Field NameDescription
Operation IDA unique identifier automatically generated by the system to distinguish each operation record.
UsernameThe user account name performing the operation.
Operation TypeIndicates the source type of the operation, such as Robot, System, Manual, etc.
Resource TypeThe category of the resource being operated on, such as LiteRobot, DataSet, etc.
Resource Unique IDThe unique ID of the corresponding resource, used to precisely locate the specific object.
Action TypeIndicates the type of operation performed, such as Create, Update, Publish, Publicize, etc.
Creation TimeThe specific timestamp when the operation occurred, used for auditing and time sorting.