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

Queue for Sentry requests #10

Open
aglitchman opened this issue Aug 25, 2024 · 0 comments
Open

Queue for Sentry requests #10

aglitchman opened this issue Aug 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@aglitchman
Copy link
Member

Is your feature request related to a problem? Please describe.
Sentry has rate limit, returns status 429:

{ --[[00000184BFE6DFD0]]
  response = "{"detail":"Sentry dropped data due to a quota or internal rate limit being reached. This will not affect your application. See https://docs.sentry.io/product/accounts/quotas/ for more information."}",
  headers = { --[[00000184BFE6E150]]
    cross-origin-resource-policy = "cross-origin",
    strict-transport-security = "max-age=31536000; includeSubDomains; preload",
    content-type = "application/json",
    content-length = "198",
    retry-after = "60",
    x-sentry-rate-limits = "60:default;error;security;attachment:organization:error_usage_exceeded",
    server = "nginx",
    access-control-allow-origin = "*",
    alt-svc = "h3=":443"; ma=2592000,h3-29=":443"; ma=2592000",
    vary = "origin,access-control-request-method,access-control-request-headers",
    via = "1.1 google",
    date = "Sun, 25 Aug 2024 14:12:57 GMT",
    access-control-expose-headers = "x-sentry-error,x-sentry-rate-limits,retry-after"
  },
  status = 429
}

Describe the solution you'd like
Create a message queue so that errors and messages for Sentry are sent at a specific rate.

@aglitchman aglitchman added the enhancement New feature or request label Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant