JayajP opened a new pull request, #29098:
URL: https://github.com/apache/beam/pull/29098
Implement the following set of metrics in BigQuery's StorageWriteAPI
transforms. These metrics will be stored in the PerWorkerMetrics container
defined in (#28923)
1. `AppendRowsRowStatus` Counter
Metric that tracks the status of BigQuery rows after making an AppendRows
RPC call.
- If the AppendRows RPC succeeds, it tracks the number of rows that been
successfully scheduled for a flush.
- If the AppendRows RPC fails, it tracks the number of rows that will be
retried and failed.
Metric has labels the following labels:
- `RowStatus`: Status of the BigQuery rows after , one of `SUCCESSFUL`,
`RETRIED`, `FAILED`
- `Status`: gRPC status of the AppendRows RPC
- `TableId`: 'datasets/{ }/tables/{ }' that the rows are sent to.
2. `ThrottledTime` Counter
Tracks the total time spent waiting between RPC retries.
Metric has labels the following labels:
- `Method`: BigQuery method that's causing the throttle. One of
`AppendRows`, `FlushRows`, `FinalizeStream`.
3. `RpcRequests` Counter
Tracks the Rpc Status of various BigQuery write methods.
Metric has labels the following labels:
- `Method`: BigQuery sink method. One of `AppendRows`, `FlushRows`,
`FinalizeStream`.
- `Status`: gRPC status of the AppendRows RPC
- `TableId`: 'datasets/{ }/tables/{ }' that the rows are sent to.
4. `RpcLatency` Histogram:
Tracks the Rpc Latency of various BigQuery write methods.
Metric has labels the following labels:
- `Method`: BigQuery sink method. One of `AppendRows`, `FlushRows`,
`FinalizeStream`.
------------------------
Thank you for your contribution! Follow this checklist to help us
incorporate your contribution quickly and easily:
- [ ] Mention the appropriate issue in your description (for example:
`addresses #123`), if applicable. This will automatically add a link to the
pull request in the issue. If you would like the issue to automatically close
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
- [ ] Update `CHANGES.md` with noteworthy changes.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
See the [Contributor Guide](https://beam.apache.org/contribute) for more
tips on [how to make review process
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
To check the build health, please visit
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
GitHub Actions Tests Status (on master branch)
------------------------------------------------------------------------------------------------
[](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more
information about GitHub Actions CI or the [workflows
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md)
to see a list of phrases to trigger workflows.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
