Uniform metrics step name semantics
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
Agree on and implement uniform metrics step name semantics which runners would adhere to.
Current discussion seems to point at a string with the pipeline graph path to the step's transform. Something along the lines of: "PBegin/SomeInputTransform/SomeParDo/...MyTransform.#Running_number_for_collisions".
Also agree on and implement metrics querying semantics. Current discussion seems to point at a substring or regex matching of steps on given string input.
[Original dev list discussion](https://lists.apache.org/thread.html/476bf8f8b1bd63ec49a9f4f45d87402d49b9c887216f3b54cb748a12@%3Cdev.beam.apache.org%3E)
Imported from Jira [BEAM-1344](https://issues.apache.org/jira/browse/BEAM-1344). Original Jira may contain additional context.
Reported by: aviemzur.
Contributor guide
Research direction
Start by reading the linked dev list discussion and the original Jira BEAM-1344 for the unresolved context. Identify the runner and metrics-querying entry points that implement current step names, then define completion as an agreed naming scheme adopted by runners and matching semantics implemented for queries.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100