Skip to content

feat: configurable provider channel buffer length #4364

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

siavashs
Copy link
Contributor

@siavashs siavashs commented Apr 23, 2025

This change makes the memory provider channel buffer length configurable.
The previously hard-coded value of 200 is used as default.
Bumping this value should result in better performance and less timeouts during sudden alert spikes, specially if the pipeline speed is affected by slow receivers.

@siavashs siavashs force-pushed the feat-alert-channel-buffer-length-config branch from 0d7fa59 to ced40e2 Compare April 23, 2025 12:11
This change makes the memory provider channel buffer length configurable.
The previously hard-coded value of 200 is used as default.
Bumping this value should result in better performance and less timeouts during sudden alert spikes,
specially if the pipeline speed is affected by slow receivers.

Signed-off-by: Siavash Safi <siavash@cloudflare.com>
@grobinson-grafana
Copy link
Collaborator

Discussed here. I'm not against making this configurable, but I'm concerned that we don't understand enough about how and why this channel is becoming full and blocking. I've asked if we can get some profiles to better understand this.

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.

2 participants