Help Center/ Cloud Service Engine/ User Guide/ ServiceComb Engines/ Service Scenario Governance (Applicable to ServiceComb Engine 2.x)/ Creating a Service Scenario
Updated on 2025-09-19 GMT+08:00
View PDF
Share

Creating a Service Scenario

You can create service scenarios based on your service process and requirements, and implement governance policies accordingly to ensure stable and efficient service running.

Prerequisites

  • You have deployed an application by referring to Creating and Deploying a Component.
  • You need to understand the API design of the microservice to be governed and create service scenarios based on the API features.

Creating a Service Scenario

  1. Log in to CSE.
  2. Choose Exclusive ServiceComb Engines.
  1. Click the target engine.
  2. Choose Service Scenario Governance.

    If the ServiceComb engine version is 2.0.0 or later but earlier than 2.4.0, choose Microservice Governance.

    • For engines with security authentication disabled, go to 6.
    • For engines with security authentication enabled, if the login user is the user imported in Importing an IAM Account, go to 6. For other users, go to 5.

  3. In the displayed Security Authentication dialog box, enter the account name and password, and click OK.

  4. Choose Service Scenarios > Create Service Scenario and set parameters by referring to the following table.

    Parameter

    Description

    Scenario

    Enter a service scenario name. Enter up to 20 characters.

    Environment

    Select a microservice environment.

    Application

    Select the application to which the service scenario to be created belongs.

    Matching Rule

    You can set Method, Path, and Headers rules to filter requests that meet specific conditions. Only requests that meet these rules are included in the created service scenario, which facilitates centralized governance of specific types of requests.

    Click Add Matching Rule to set the request marker.

    • Method: (Mandatory) Select the method of marking the traffic request feature. The GET, PUT, POST, DELETE, and PATCH methods are supported.
    • Path: (Mandatory) Set features contained in the traffic request URI.
    • Headers: (Optional) Click Add Headers Rule and set the marker of the traffic request header.

  5. Click OK. When a service scenario is created, the configuration starting with servicecomb.matchgroup. is automatically generated.

    • Click in the row that contains a service scenario to view the matching rule details.
    • Click Edit in the Operation column of a service scenario to edit the service scenario.
    • Click Delete in the Operation column of a service scenario to delete the service scenario.