Why only one trace_span data in Telecom dataset?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 423
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
Hi, thank you for the excellent work on processing the original AIOps 2020 and AIOps 2021 Challenge datasets.
I had a quick question regarding the AIOps 2020 (Telecom) data. In the original version, there are six types of trace data available for each day, as shown here:
,
However, in your processed version, it seems only the trace_jdbc data has been retained. Could you share the reasoning behind this choice? I’m trying to understand how the partial trace data (e.g., cmdb_id such as docker_006 and dsName such as db_003) are meant to be related to the OS components that appear in the record.csv file as ground truth.
THANK YOU,
best,
Yi
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the original AIOps 2020 Telecom data with the processed dataset, focusing on the six trace types and the retained trace_jdbc data. Examine how cmdb_id and dsName relate to the OS components in record.csv. Done means documenting the retention rationale and the relationship between the partial trace data and the ground truth.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100