[Documentation Request]: Including reference to Dataflow Metrics exporter tool in README.md

[prathapreddy123]

What would you like to happen?

Recently launched a Metrics exporter CLI tool that fetches the dataflow job metrics, estimates job cost and stores the results either in BQ or GCS. Interested in including the reference in README under learn more section.

@svetakvsundhar

Issue Priority

Priority: 3 (nice-to-have improvement)

Issue Components

• [ ] Component: Python SDK
• [ ] Component: Java SDK
• [ ] Component: Go SDK
• [ ] Component: Typescript SDK
• [ ] Component: IO connector
• [ ] Component: Beam YAML
• [ ] Component: Beam examples
• [ ] Component: Beam playground
• [ ] Component: Beam katas
• [ ] Component: Website
• [ ] Component: Spark Runner
• [ ] Component: Flink Runner
• [ ] Component: Samza Runner
• [ ] Component: Twister2 Runner
• [ ] Component: Hazelcast Jet Runner
• [ ] Component: Google Cloud Dataflow Runner

[svetakvsundhar]

@damccorm @liferoad -- can we add this in our Beam ReadMe even though it isn't necessarily maintained by the "Beam" community?

I'm thinking we can add a section called "third party projects" that lists projects like this, Dataflow Templates, Scio, etc. We could perhaps add this into our readMe and create a new page on the Beam website. Wdyt?

[damccorm]

I wouldn't include third party projects in the Readme, I think the Readme should ideally be succinctly focused on the core value offering of Beam. I think adding a website page is a good idea, I'd support a pr like that