[GitHub] [skywalking] Gallop-stark commented on issue #6876: mesh url level accesslog metrics

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

Gallop-stark commented on issue #6876:
URL: https://github.com/apache/skywalking/issues/6876#issuecomment-830476994


   Thank you for your reply!
   
   > From the unified metrics, the endpoint grouping mechanism is existing for a while in SkyWalking.You could do this today.
   
   I find this, [docs/en/setup/backend/endpoint-grouping-rules.md](https://github.com/apache/skywalking/blob/83757dae617f3ff5b0a61fc8985b859f28979974/docs/en/setup/backend/endpoint-grouping-rules.md),i do not know whether or not i found right md.
   
   Maybe my enviroment is different from skywalking.
   
   In this md,i know the endpoint grouping mechanism need users add regex pattern manually,but in my environment,many service have many regex patterns, users will feel troubled to add so manay patterns, so this is why i design this learning algorithm.I know real url is better, but in my enviroment, too many real url and too many regex patterns,and all request must be detected.
   
   Yes,languge agent can get real regex pattern in code, but i think it not suitable for mesh gateway detection.There are reason:
   1. Here are java, php, nodejs, python, go, c++ ... in my environment,make every language agent need so many time,and need new agent if add a new language.
   2. I think mesh gateway should detect all input request, the real regex pattern in code obtained by language agent is code expected reqeust, maybe input request has some url request that code not excepted and should be detect by mesh, so mesh gateway detection is different from language agent.
   
   I will be appreciated if you can give me some suggestions.
   
   thanks.
   
   


-- 
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