wu-sheng opened a new issue, #9676: URL: https://github.com/apache/skywalking/issues/9676
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar feature requirement. ### Description As we have the virtual database and cache analysis in 9.3.0, let's bring the last missing core analysis, virtual MQ, into the backend analysis. As we designed years ago, span layer includes the following options ```java public enum SpanLayer { DB(1), RPC_FRAMEWORK(2), HTTP(3), MQ(4), CACHE(5); ``` MQ span layer represents a queue server with consumer and producer sides, such as, Kafka, RocketMQ, and Pulsar. SkyWalking Java agent has had plugins for these typical and widely used MQ's Java clients for years too. Now, let's analyze their access load(producing/consuming load), such as X messages per second, and other typical metrics There is one special about time, MQ is able to consume and produce messages in bulk mode, and some queue clients are using pulling mode(typically Kafka), so the span could only include pulling time, but, meanwhile, some pushing mode client span could including all further processes' time. Also, `endpoint_mq_consume_count` and `endpoint_mq_consume_latency` are purely analyzed through OAL, even having tag match expression, we should consider merging it in a consistent way like existing `VirtualServiceProcessor` implementations. ### Use case _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
