alibaba / alibaba/clusterdata

Confused of identifying services from MS_CallGraph_Table in MicroserviceTrace-v2021

Open
#157 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
2.2k
Forks
482
PR merge metrics
No merged PRs in 30d

Description

Hi, I am trying to identify the services from MS_CallGraph_Table in MicroserviceTrace-v2021, and analyze the dynamic call graphs for each service.

I follow the next steps to do this:
1. Using the "traceid" to identify each call graph, and I find there are about **9 million** call graphs (requests) in the traces.
2. In each traceid (request), I try to find the entering call with the rpcid of 0.1 or 0.1.1 and the rpctype of HTTP or userdefined, and record the corresponding calls. But I find about **1 million** of the Call Graphs cannot find this kind of call. Some traceid even has a rpcid with '0' like the following figure. In the following figure, what the record with rpcid with '0' represents, and which record is the entering call?
![image](https://user-images.githubusercontent.com/34558335/199450284-999ac572-5bc2-48b7-9e08-722902bac457.png)
3. With the finding entering calls in step 2, I use the combination of (dm, interface) to identify different services. But I find there are **8000+** services in the traces, which is inconsistent with the paper in SoCC'21 (**3000+** services). Moreover, more than **5000+** services only have one request in the traces. This looks strange.
4. I use the service with the most requests to plot the requests per minute as the figure as follows. It seams that there is no requests for half of the total time in the trace. This also looks strange.
image

**Is there any problem with my method to identify services? If not, why there exists these strange cases?**

Thank you very much!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the MS_CallGraph_Table schema and the MicroserviceTrace-v2021 documentation, focusing on traceid, rpcid, rpctype, dm, and interface. Reproduce the service grouping and request-count checks described in the issue, then document how entering calls and services should be identified and explain the reported anomalies.

Written by the indexing model from the issue text.

Assessment

Domain
data, distributed-systems
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.