[BEAM-147] Introduce an easy API for pipeline metrics

• Type: New Feature
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: beam-model, sdk-java-core, sdk-py-core
• Labels: Done
• Assignee: Ben Chambers
• Reporter: Robert Bradshaw
• Created: 23/Mar/16 22:21
• Updated: 06/Oct/20 21:57
• Resolved: 26/Mar/18 16:52

Description

The existing Aggregators are confusing both because of their name and because they serve multiple purposes.

Previous discussions around Aggregators/metrics/etc:
Discussion on user list
Discussion on dev list
Exact name still being bikeshedded.

Design document

Issue Links

• links to: GitHub Pull Request #1024
• links to: GitHub Pull Request #1419
• links to: GitHub Pull Request #1420
• links to: GitHub Pull Request #1420
• links to: GitHub Pull Request #1761
• links to: GitHub Pull Request #1763

Sub-Tasks

• Implement Metrics support for Dataflow Runner: Resolved
• Implement Metrics support for Flink runner: Resolved
• Implement Metrics support for Spark runner: Resolved
• Remove Aggregators from the Java SDK: Resolved
• Update Javadoc/Examples/etc.: Open
• MetricsTest matchers should loosen expectations on attempted values: Resolved