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

feat(ourlogs): Add log ingestion sample rate #85684

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

k-fish
Copy link
Member

@k-fish k-fish commented Feb 21, 2025

Summary

We're moving to sharing the EAP cluster for logs. In order to safely roll out logs onto the existing cluster, we want to be able to control processing into the kafka topics, consumers and storage, one project at a time in production.

For rolling out ingestion, especially with shared usage of the EAP cluster, we want to be able to control processing into the kafka topics, consumers and storage.
@k-fish k-fish self-assigned this Feb 21, 2025
@k-fish k-fish requested a review from a team as a code owner February 21, 2025 20:53
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Feb 21, 2025
@k-fish k-fish merged commit 9a8e9ba into master Feb 24, 2025
50 checks passed
@k-fish k-fish deleted the feat/ourlogs/add-log-ingestion-project-sample-rate branch February 24, 2025 16:07
k-fish added a commit to getsentry/relay that referenced this pull request Feb 24, 2025
### Summary
We're moving to sharing the EAP cluster for logs. In order to safely
roll out logs onto the existing cluster, we want to be able to control
processing into the kafka topics, consumers and storage, one project at
a time in production.

Needs: getsentry/sentry#85684
@github-actions github-actions bot locked and limited conversation to collaborators Mar 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants