You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
The text was updated successfully, but these errors were encountered: