Create a time correlation telemetry & calculation output product suitable for thorough analysis
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
The basic idea is to have a human + machine-readable log of all time correlation telemetry, along with associated metrics.
Purposes for use would include:
- Aiding in allowing systems and TK engineers to run their own analysis & answer questions when interesting or anomalous situations arise
- Aiding in the ability for lossless reingestion of time correlation telemetry, via a new TelemetrySource implementation (and which would deprecate the Raw Telemetry Table as a telemetry source)
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 locating the existing time-correlation telemetry flow, the Raw Telemetry Table, and the TelemetrySource implementations. Read how telemetry and associated metrics are currently represented and consumed. Done would require a defined human- and machine-readable output suitable for analysis and lossless reingestion, but the issue does not specify files, formats, or acceptance tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100