standardize telemetry format
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 12
- Forks
- 11
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 3
Description
Currently our CSV files are a custom format:
TIMESTAMP,CPU_USAGE_ACTUAL
2023.04.02-00:09:00:000,7.2
2023.04.02-00:10:00:000,7.04
2023.04.02-00:11:00:000,6.88
We should try to use the Open Telemetry format for consistency. Ex: timestamp as uint64.
Contributor guide
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
No file, test, or entry point is named. Read the CSV example and linked OpenTelemetry documentation first, then locate the code that produces these telemetry files. Done requires an agreed OpenTelemetry-compatible schema, including the timestamp representation, and consistent output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100