Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Viewing Service Details

Updated on 2025-01-06 GMT+08:00

After an AI application is deployed as a real-time service, you can access the service page to view its details.

  1. Log in to the ModelArts management console and choose Service Deployment > Real-Time Services.
  2. On the Real-Time Services page, click the name of the target service. The service details page is displayed.

    You can view the service name, status, and other information. For details, see Table 1.

    Table 1 real-time service parameters

    Parameter

    Description

    Name

    Name of the real-time service.

    Status

    Status of the real-time service.

    Source

    AI application source of the real-time service.

    Service ID

    Real-time service ID

    Description

    Service description, which can be edited after you click the edit button on the right side.

    Resource Pool

    Resource pool specifications used by the service. If the public resource pool is used for deployment, this parameter is not displayed.

    Custom Settings

    Customized configurations based on real-time service versions. This allows version-based traffic distribution policies and configurations. Enable this option and click View Settings to customize the settings. For details, see Modifying Customized Settings.

    Traffic Limit

    Maximum number of times a service can be accessed within a second.

    Runtime Log Output

    This function is disabled by default. The runtime logs of real-time services are stored only in the ModelArts log system.

    If this function is enabled, the runtime logs of real-time services will be exported and stored in Log Tank Service (LTS). LTS automatically creates log groups and log streams and caches run logs generated within seven days by default. For details about the LTS log management function, see Log Tank Service.

    NOTE:
    • This cannot be disabled once it is enabled.
    • You will be billed for the log query and log storage functions provided by LTS. For details, see section LTS Pricing Details.
    • Do not print unnecessary audio log files. Otherwise, system logs may fail to be displayed, and the error message "Failed to load audio" may be displayed.

    WebSocket

    Whether to upgrade to the WebSocket service.

  3. Switch between tabs on the details page of a real-time service to view more details. For details, see Table 2.
    Table 2 Details of a real-time service

    Parameter

    Description

    Usage Guides

    This page displays the API URL, AI application information, input parameters, and output parameters. You can click to copy the API URL to call the service. If application authentication is supported, you can view the API URL and authorization management details, including the application name, AppKey, and AppSecret, in the Usage Guides. You can also add or cancel authorization for an application.

    Prediction

    You can perform real-time prediction on this page. For details, see Testing the Deployed Service.

    Configuration Updates

    This page displays Current Configurations and Update History.

    • Current Configurations: AI application name, version, status, compute node specifications, traffic ratio, number of compute nodes, deployment timeout interval, environment variables, storage mounting, and resource pool information (for services deployed in a dedicated resource pool)
    • Update History: historical AI application information.

    Monitoring

    This page displays resource usage and AI application calls.

    • Resource Usage: includes the used and available CPU, memory, GPU, and NPU resources.
    • AI Application Calls: indicates the number of AI application calls. The statistics collection starts after the AI application status changes to Ready. (This parameter is not displayed for WebSocket services.)

    Event

    This page displays key operations during service use, such as the service deployment progress, detailed causes of deployment exceptions, and time points when a service is started, stopped, or modified.

    Events are saved for one month and will be automatically cleared then.

    For details about how to view events of a service, see Viewing Service Events.

    Logs

    This page displays the log information about each AI application in the service. You can view logs generated in the latest 5 minutes, latest 30 minutes, latest 1 hour, and user-defined time segment.

    You can select the start time and end time when defining the time segment.

    If this function is enabled, the logs stored in LTS will be displayed. You can click View Complete Logs on LTS to view all logs.

    Meet the following rules to search logs:

    • Do not enter strings that contain any following delimiters: ,'";=()[]{}@&<>/:\n\t\r.
    • Enter keywords for exact search. A keyword is a word between two adjacent delimiters.
    • Enter keywords for fuzzy search. For example, you can enter error, er?or, rro*, or er*r.
    • Enter phrases for exact search. For example, Start to refresh.
    • Before enabling this function, you can combine keywords with AND (&&) or OR (||). For example, query logs&&erro* or query logs||erro*. After enabling this function, you can combine keywords with AND or OR. For example, query logs AND erro* or query logs OR erro*.

    Tags

    Tags that have been added to the service. Tags can be added, modified, and deleted.

    For details about how to use tags, see How Does ModelArts Use Tags to Manage Resources by Group?

Modifying Customized Settings

A customized configuration rule consists of the configuration condition (Setting), access version (Version), and customized running parameters (including Setting Name and Setting Value).

You can configure different settings with customized running parameters for different versions of a real-time service.

The priorities of customized configuration rules are in descending order. You can change the priorities by dragging the sequence of customized configuration rules.

After a rule is matched, the system will no longer match subsequent rules. A maximum of 10 configuration rules can be configured.

Table 3 Parameters for Custom Settings

Parameter

Mandatory

Description

Setting

Yes

Expression of the Spring Expression Language (SPEL) rule. Only the equal, matches, and hashCode expressions of the character type are supported.

Version

Yes

Access version for a customized service configuration rule. When a rule is matched, the real-time service of the version is requested.

Setting Name

No

Key of a customized running parameter, consisting of a maximum of 128 characters.

Configure this parameter if the HTTP message header is used to carry customized running parameters to a real-time service.

Setting Value

No

Value of a customized running parameter, consisting of a maximum of 256 characters.

Configure this parameter if the HTTP message header is used to carry customized running parameters to a real-time service.

Customized settings can be used in the following scenarios:

  • If multiple versions of a real-time service are deployed for gray release, customized settings can be used to distribute traffic by user.
    Table 4 Built-in variables

    Built-in Variable

    Description

    DOMAIN_NAME

    Account name used to call an inference request

    DOMAIN_ID

    Account ID used to call an inference request

    PROJECT_NAME

    Project name that is used to call an inference request

    PROJECT_ID

    Project ID that invokes the inference request

    USER_NAME

    Username that is used to call an inference request

    USER_ID

    User ID that is used to call an inference request

    Pound key (#) indicates that a variable is referenced. The matched character string must be enclosed in single quotation marks.

    #{Built-in variable} == 'Character string'
    #{Built-in variable} matches 'Regular expression'
    • Example 1:

      If the account name in the inference request is User A, the specified version is matched.

      #DOMAIN_NAME == 'User A'
    • Example 2:

      If the account name in the inference request starts with op, the specified version is matched.

      #DOMAIN_NAME matches 'op.*'
      Table 5 Common regular expressions

      Character

      Description

      .

      Match any single character except \n. To match any character including \n, use (.|\n).

      *

      Match the subexpression that it follows for zero or multiple times. For example, zo* can match z and zoo.

      +

      Match the subexpression that it follows for once or multiple times. For example, zo+ can match zo and zoo, but cannot match z.

      ?

      Match the subexpression that it follows for zero or one time. For example, do(es)? can match does or do in does.

      ^

      Match the start of the input string.

      $

      Match the end of the input string.

      {n}

      n is a non-negative integer, which matches exactly n number of occurrences of an expression. For example, o{2} cannot match o in Bob, but can match two os in food.

      x|y

      Match x or y. For example, z|food can match z or food, and (z|f)ood can match zood or food.

      [xyz]

      Character set, where any single character in it can be matched. For example, [abc] can match a in plain.

      Figure 1 Traffic distribution by user
  • If multiple versions of a real-time service are deployed for gated launch, customized settings can be used to access different versions through the header.
    Start with #HEADER_ to indicate that the header is referenced as a condition.
    #HEADER_{key} == '{value}'
    #HEADER_{key} matches '{value}'
    • Example 1:

      If the header of an inference HTTP request contains a version and the value is 0.0.1, the condition is met. Otherwise, the condition is not met.

      #HEADER_version == '0.0.1'
    • Example 2:

      If the header of an inference HTTP request contains testheader and the value starts with mock, the rule is matched.

      #HEADER_testheader matches 'mock.*'
    • Example 3:

      If the header of an inference HTTP request contains uid and the hash code value meets the conditions described in the following algorithm, the rule is matched.

      #HEADER_uid.hashCode() % 100 < 10
      Figure 2 Using the header to access different versions
  • If a real-time service version supports different runtime configurations, you can use Setting Name and Setting Value to specify customized runtime parameters so that different users can use different running configurations.

    Example:

    When user A accesses the AI application, the user uses configuration A. When user B accesses the AI application, the user uses configuration B. When matching a running configuration, ModelArts adds a header to the request and also the customized running parameters specified by Setting Name and Setting Value.
    Figure 3 Customized running parameters added for a customized configuration rule

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback