Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set default send_batch_max_size on k8s cluster receiver #717

Merged
merged 1 commit into from
Apr 3, 2023

Conversation

dmitryax
Copy link
Contributor

@dmitryax dmitryax commented Apr 2, 2023

Big k8s clusters with many pods cause the k8s cluster receiver to fetch metrics batches with many data points which leads to timeouts on signalfx exporter.

This change introduces a maximum limit of data points that one metrics batch can contain. Batches with more than 32k data points will be broken down in several batches.

Resolves #716

@dmitryax dmitryax requested review from a team as code owners April 2, 2023 21:12
@dmitryax dmitryax force-pushed the set-send_batch_max_size-default branch from 8e341cb to 6cc0884 Compare April 2, 2023 21:17
Big k8s clusters with many pods cause k8s cluster receiver to fetch metrics batches with huge number of datapoints that are timing to be sent on signalfx exporter.

This change introduces maximum limit of datapoints that one metrics batch can contain. batches with more than 64k datapoints will be broken in several batches
@dmitryax dmitryax force-pushed the set-send_batch_max_size-default branch from 6cc0884 to d380b76 Compare April 2, 2023 21:19
@dmitryax dmitryax merged commit c8c1136 into signalfx:main Apr 3, 2023
@dmitryax dmitryax deleted the set-send_batch_max_size-default branch April 10, 2023 21:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Limit metric batches size produced by k8s cluster receiver to avoid timeout
2 participants