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

[OTLP Log] Gateway performance evaluation #1289

Closed
a-thaler opened this issue Jul 18, 2024 · 2 comments · Fixed by #1318
Closed

[OTLP Log] Gateway performance evaluation #1289

a-thaler opened this issue Jul 18, 2024 · 2 comments · Fixed by #1318
Assignees
Labels
area/logs LogPipeline
Milestone

Comments

@a-thaler
Copy link
Collaborator

Description
In order to go with the targetted architecture as outlined in #556, it is crucial to understand if bigger cluster setups can be realized even without having an auto scaling of the gateway in place. If that is not the case, an alternative setup might be possible where the agent is encompassing the all gateway logic additional and pushs directly to the target.

Goal
Understand how much a typical gateway setup can handle, assuming the ideal backend. Is the performance that well already, that anyway backends cannot handle this high volume of logs?

Criterias

  • High log volume tests are executed with a two replica gateway setup doing similar logic as in the metric gateway
  • Results are documented as well as conclusions on if a non-auto-scaling gateway setup is tolerable for the MVP

Reasons

Attachments

Release Notes


@a-thaler a-thaler added the area/logs LogPipeline label Jul 18, 2024
@a-thaler a-thaler mentioned this issue Jul 18, 2024
23 tasks
@k15r
Copy link
Contributor

k15r commented Jul 22, 2024

Come up with a sizing definition for a single gateway instance:

  • needs to be able to handle the maximum load accepted by a "regular" CLS instance

  • use the same log definition as used by CLS

  • Push logs using telemetrygen

@k15r k15r self-assigned this Jul 23, 2024
@k15r
Copy link
Contributor

k15r commented Aug 12, 2024

#1318

@k15r k15r linked a pull request Aug 12, 2024 that will close this issue
5 tasks
@a-thaler a-thaler added this to the 1.22.0 milestone Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logs LogPipeline
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants