alibaba / alibaba/clusterdata

Clarification of timestamps in MS_CallGraph_Table (2021 trace dataset)

Open
#156 2 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

Thanks for offering such a great trace dataset.

I'm wondering the timestamp in MS_CallGraph_Table is collected from the serverside or clientside. For example, is the timestamp recorded from a machine(host) running um or a machine(host) running dm?

| columns | Example Entry |
|:---------:|------------------------------------------------------------------|
| timestamp | 16397576 |
| traceid | 015101cd15919399974329000e |
| rpcid | 0.1.1.2.50 |
| um | 35114acfb54c54fb9618f23cd28bbc57c765f597df140977d7030dcc52775ed4 |
| rpctype | rpc |
| interface | af42b5e3e0eb334d38619733586d78d1414f6549f24d31b39a5294454638bc59 |
| dm | b65fdc9bfef6b4974c3e90e1ec7b92d30e639789da5a78c1d4685857e19c75a0 |
| rt | 13 |

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the 2021 trace dataset documentation or metadata for MS_CallGraph_Table, then inspect the timestamp, um, and dm fields together. Done means the documentation explicitly states whether the timestamp is measured on the client-side or server-side and identifies the corresponding host.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.