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

[Request]: Small update to serverless limitations doc page #4583

Open
chrisdistasio opened this issue Nov 26, 2024 · 0 comments · May be fixed by #4584
Open

[Request]: Small update to serverless limitations doc page #4583

chrisdistasio opened this issue Nov 26, 2024 · 0 comments · May be fixed by #4584

Comments

@chrisdistasio
Copy link

chrisdistasio commented Nov 26, 2024

Description

We have a "limitations" page in the serverless docs which explains that a user may experience rate limiting or ingest failures if they surpass 11.5mb/s ingest via MIS.

Currently, the maximum ingestion rate for the Managed Intake Service (APM and OpenTelemetry ingest) is 11.5 MB/s of uncompressed data (roughly 1TB/d uncompressed equivalent). Ingestion at a higher rate may experience rate limiting or ingest failures.

While we do not plan to remove this limitation while using current queueing technology, we can adjust it (internally) as appropriate. Note: we also monitor for customers who might be experiencing rate limiting.

I'm suggesting adding the following text at the end of the current doc:

"If you believe you are experiencing rate limiting or other ingest-based failures, please contact customer support for assistance."

It would be nice if we could include a link to customer support.

Resources

Spoke live with Dede about this.

Which documentation set does this change impact?

Serverless only

Feature differences

Serverless only as it relates to MIS

What release is this request related to?

N/A

Collaboration model

The documentation team

Point of contact.

Main contact: @chrisdistasio

Stakeholders: @simitt @lucabelluccini

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants