<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
<!-- Issue number if applicable -->
Forgot to do this on #11561
#### Description
[mdatagen] support using a different github project in mdatagen README
issues list
Uses a a new configuration property `github_project` on mdatagen
configuration.
#### Link to tracking issue
Fixes
https://github.com/open-telemetry/opentelemetry-collector/issues/9240
---------
Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Co-authored-by: Alex Boten <223565+codeboten@users.noreply.github.com>
This PR improves the description of the send_batch_size configuration option in the batch processor. The current documentation may not be 100 percent clear to new users of the processor. This change seeks to add clarification that send_batch_size is just a trigger to send and does not enforce limits.
Implement the fixes proposed in #7508. Otherwise, using a batchprocessor with Config{} passes validation but acts badly at runtime there is both a zero-duration timer and the call to sendItems never returns, constantly sending empty batches.
**Link to tracking Issue:** #2754
This change introduces a BenchmarkBatchMetricProcessor that stress tests batching logic.
Results before:
`BenchmarkBatchMetricProcessor-12 20000 80614 ns/op`
Results after the change:
`BenchmarkBatchMetricProcessor-12 20000 96184 ns/op`
Pablo Baeyens