[GitHub] [skywalking] hanahmily commented on a change in pull request #4802: Group Parameterized Endpoints

[GitBox <gi...@apache.org>]

hanahmily commented on a change in pull request #4802:
URL: https://github.com/apache/skywalking/pull/4802#discussion_r428077305



##########
File path: docs/en/setup/backend/endpoint-grouping-rules.md
##########
@@ -0,0 +1,23 @@
+# Group Parameterized Endpoints
+In most cases, the endpoint should be detected automatically through the language agents, service mesh observability solution, 
+or configuration of meter system.
+
+There are some special cases, especially when people use REST style URI, the application codes put the parameter in the endpoint name, 
+such as putting order id in the URI, like `/prod/ORDER123` and `/prod/ORDER123`. But logically, people expect they could
+have an endpoint name like `prod/{order-id}`. This is the feature of parameterized endpoint grouping designed for.
+
+Current, user could set up grouping rules through the static YAML file, named `endpoint_name_grouping.yml`,
+or use [Dynamic Configuration](dynamic-config.md) to initial and update the endpoint grouping rule.
+
+## Configuration Format
+No matter in static local file or dynamic configuration value, they are sharing the same YAML format.
+
+```yaml
+grouping:
+  # Endpoint of the service would follow the following rules
+  - service-name: serviceA

Review comment:
       For HTML and static asserts, a global rule might be more helpful. BTW do we have rule to filter out static resources when users intend to get rid of them.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org