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

perf(opentelemetry): increase queue max batch size #12488

Merged
merged 1 commit into from
Feb 1, 2024

Conversation

samugi
Copy link
Member

@samugi samugi commented Feb 1, 2024

Summary

The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation.

Checklist

Issue reference

https://konghq.atlassian.net/browse/KAG-3173

The max batch size for Opentelemetry was set to the default value: 1
the value actually refers to the number of spans in a batch, so we are
increasing the default value to 200 which corresponds to what the
default value used to be with the "old" queue implementation.
@samugi samugi force-pushed the chore/otel-queue-max-batch-size branch from 0df0e06 to 5d3c48e Compare February 1, 2024 15:10
@samugi samugi added the cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee label Feb 1, 2024
@bungle bungle merged commit c7cb900 into master Feb 1, 2024
51 checks passed
@bungle bungle deleted the chore/otel-queue-max-batch-size branch February 1, 2024 18:21
@team-gateway-bot
Copy link
Collaborator

Backport failed for release/3.3.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release/3.3.x
git worktree add -d .worktree/backport-12488-to-release/3.3.x origin/release/3.3.x
cd .worktree/backport-12488-to-release/3.3.x
git switch --create backport-12488-to-release/3.3.x
git cherry-pick -x c7cb900f4919e6b320b7bdf9132cfa4747679760

github-actions bot pushed a commit that referenced this pull request Feb 1, 2024
The max batch size for Opentelemetry was set to the default value: 1
the value actually refers to the number of spans in a batch, so we are
increasing the default value to 200 which corresponds to what the
default value used to be with the "old" queue implementation.

(cherry picked from commit c7cb900)
@team-gateway-bot
Copy link
Collaborator

Successfully created backport PR for release/3.4.x:

github-actions bot pushed a commit that referenced this pull request Feb 1, 2024
The max batch size for Opentelemetry was set to the default value: 1
the value actually refers to the number of spans in a batch, so we are
increasing the default value to 200 which corresponds to what the
default value used to be with the "old" queue implementation.

(cherry picked from commit c7cb900)
@team-gateway-bot
Copy link
Collaborator

Successfully created backport PR for release/3.5.x:

bungle pushed a commit that referenced this pull request Feb 1, 2024
The max batch size for Opentelemetry was set to the default value: 1
the value actually refers to the number of spans in a batch, so we are
increasing the default value to 200 which corresponds to what the
default value used to be with the "old" queue implementation.

(cherry picked from commit c7cb900)
samugi added a commit that referenced this pull request Feb 2, 2024
The max batch size for Opentelemetry was set to the default value: 1
the value actually refers to the number of spans in a batch, so we are
increasing the default value to 200 which corresponds to what the
default value used to be with the "old" queue implementation.

(cherry picked from commit c7cb900)
samugi added a commit that referenced this pull request Feb 2, 2024
The max batch size for Opentelemetry was set to the default value: 1
the value actually refers to the number of spans in a batch, so we are
increasing the default value to 200 which corresponds to what the
default value used to be with the "old" queue implementation.
hanshuebner pushed a commit that referenced this pull request Feb 5, 2024
The max batch size for Opentelemetry was set to the default value: 1
the value actually refers to the number of spans in a batch, so we are
increasing the default value to 200 which corresponds to what the
default value used to be with the "old" queue implementation.
@team-gateway-bot
Copy link
Collaborator

Backport failed for release/3.3.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release/3.3.x
git worktree add -d .worktree/backport-12488-to-release/3.3.x origin/release/3.3.x
cd .worktree/backport-12488-to-release/3.3.x
git switch --create backport-12488-to-release/3.3.x
git cherry-pick -x c7cb900f4919e6b320b7bdf9132cfa4747679760

@team-gateway-bot
Copy link
Collaborator

Backport failed for release/3.4.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release/3.4.x
git worktree add -d .worktree/backport-12488-to-release/3.4.x origin/release/3.4.x
cd .worktree/backport-12488-to-release/3.4.x
git switch --create backport-12488-to-release/3.4.x
git cherry-pick -x c7cb900f4919e6b320b7bdf9132cfa4747679760

@team-gateway-bot
Copy link
Collaborator

Backport failed for release/3.5.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release/3.5.x
git worktree add -d .worktree/backport-12488-to-release/3.5.x origin/release/3.5.x
cd .worktree/backport-12488-to-release/3.5.x
git switch --create backport-12488-to-release/3.5.x
git cherry-pick -x c7cb900f4919e6b320b7bdf9132cfa4747679760

github-actions bot pushed a commit that referenced this pull request Feb 6, 2024
The max batch size for Opentelemetry was set to the default value: 1
the value actually refers to the number of spans in a batch, so we are
increasing the default value to 200 which corresponds to what the
default value used to be with the "old" queue implementation.

(cherry picked from commit c7cb900)
@team-gateway-bot
Copy link
Collaborator

Successfully created cherry-pick PR for master:

@team-gateway-bot
Copy link
Collaborator

Successfully created backport PR for release/3.6.x:

bungle pushed a commit that referenced this pull request Feb 13, 2024
The max batch size for Opentelemetry was set to the default value: 1
the value actually refers to the number of spans in a batch, so we are
increasing the default value to 200 which corresponds to what the
default value used to be with the "old" queue implementation.

(cherry picked from commit c7cb900)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants