This section introduces the HermesAgent observability application for large model observability, available in the TLS application marketplace.

Overview

By integrating the HermesAgent observability application, you can monitor data and access services such as the HermesAgent observability dashboard and Trace call chain.

Monitoring chart details

The monitoring chart details for the TLS HermesAgent observability application are as follows:

HermesAgent observability dashboard

Type	Chart
Model invocation	Total tokens, daily tokens, input tokens, output tokens Cache Read Tokens, Cache Write Tokens, Reasoning Tokens, Prompt Tokens Model token consumption distribution, provider token consumption distribution, platform token consumption distribution Number of requests, daily model invocation count, model invocation latency P90
Session analysis	Number of new sessions, daily new session count, daily conversation count New session platform distribution, new session model distribution Conversation platform distribution, conversation model distribution, conversation count, conversation P90 latency
Tool invocation	Total tool invocations, daily tool invocations, tool invocation P90 latency, tool invocation P90 latency distribution Tool invocation distribution, tool invocation failure distribution Successful tool invocation count, failed tool invocation count
O&M analysis	Error log distribution Daily error logs

Trace Call Chain

Type
Chart
Trace analysis
Trace analysis (data retrieval limit: 50,000 records)

Topic list

Displays the corresponding projects and log topics for HermesAgent logs and Trace logs.

Integrate log applications

Limitations

Category	Description
Region restriction	The server where HermesAgent is deployed and TLS must be in the same region to ensure network connectivity.
Authentication method	HermesAgent access to TLS supports the following authentication methods: AK/SK: AccessKey ID and AccessKey Secret for Volcengine accounts. Supports automatic creation of TLS resources (project/app/topic) and auto-generates log topic IDs. It is recommended for standalone trials and integration testing. API Key: A key credential for requesting Volcano TLS. It is used only for reporting Log, Metric, and Trace data. Enforces strict permissions and does not support auto creation of TLS resources. It is suitable for multi-data center environments and strict permission management scenarios. Notice API Key is a closed beta feature. If needed, contact your account manager for access to the allowlist.

Integration steps

Integrate the HermesAgent log application.

Log in to TLS console.

Select the region where log service is located from the top navigation bar.

In the left navigation bar, click Common functions > Log application.

On the App store tab, on the HermesAgent card, click Integrated application.

Configure the following integration parameters, and then click Integration template.

Parameters	Description
Name	Name of the application integration. Only Chinese characters, letters, numbers, underscores _, and hyphens - are allowed. Can not start or end with a hyphen - Length must be between 3 and 64 characters.
Description	Description of the application integration. Length limit: 0–64 characters. Angle brackets <>, apostrophes ', backslashes \, double quotes ", and emojis are not supported.
Log project	Select the project where data will be stored.

After a successful integration, the dashboard page of the TLS application is displayed by default.

Install the HermesAgent plugin.

Log in to the server where HermesAgent is deployed.

Depending on the installation method, execute the following commands.

AK/SK mode
API Key mode

One-click installation script, suitable for development and testing environments. You must obtain the AccessKey ID and AccessKey Secret of the Volcano Engine account in advance.

curl -fsSL https://tls-hermes-cn-beijing.tos-cn-beijing.volces.com/install.sh | bash -s -- \
--region cn-beijing \
--ak {YourAK} \
--sk {YourSK} \
--endpoint tls-cn-beijing.volces.com \
--non-interactive

After installation is complete, execute the following command to restart the Gateway.

hermes gateway restart

After the restart is complete, execute the following command to check the plugin status.

If the plugin status is running, the installation is successful. At this point, you can view the log application observability dashboard in the TLS Console.

hermes plugins list

Manage my applications

After successful integration of the log application, you can perform the following management operations on the integrated log applications:

Log in to TLS console.

Select the region where log service is located from the top navigation bar.

In the left navigation bar, click Common functions > Log application.

Go to the My app tab. In the Actions column of the corresponding log application, the following management operations are supported:

Actions	Description
Access management	Click Access management to enter the Access management tab, where you can modify the name and description of the log application.
Cancel access	Click Cancel access, confirm the information in the cancel access pop-up window, and then click Cancel access again.

Type	Chart
Trace analysis	Trace analysis (data retrieval limit: 50,000 records)

Torch Log Service