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.

Sign up for GitHub

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

Jump to bottom

Update how-new-relic-distributed-tracing-works.mdx to add info about limits now visible in the limits UI. #19074

Merged
merged 2 commits into from
Oct 28, 2024
Merged

Update how-new-relic-distributed-tracing-works.mdx to add info about limits now visible in the limits UI. #19074

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c1a55ca
Update how-new-relic-distributed-tracing-works.mdx
beatface Oct 24, 2024
30d7385
style(Distributed tracing): Added TW edits
nbaenam Oct 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...t/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -201,7 +201,7 @@ Some of our tools don't use sampling. Sampling details for these tools:

### Trace limits [#trace-limits]

Our data processing systems are equipped with internal limits in order to protect our infrastructure from unexpected data surges. This protective layer not only maintains the integrity of our platform but also ensures a dependable and consistent experience for all our customers. While these limits are adjusted as-needed based on various conditions, they're set with a forward-looking approach. As our user base and data intake grow, we expand our infrastructure capacity. This commitment ensures that we capture all customer data sent our way and offer you a clear and uninterrupted view into your trace data.
Our data processing systems include internal limits to protect our infrastructure from unexpected data surges: Trace API, agent spans, browser spans, mobile spans, and lambda spans. This protective layer not only maintains the integrity of our platform but also ensures a dependable and consistent experience for all our customers. We adjust these limits as needed based on various conditions, but they're set with a forward-looking approach. As our users and data grow, we expand our infrastructure capacity and raise these limits. This commitment ensures that we capture all customer data sent our way and offer you a clear and uninterrupted view into your trace data. To check if you are hitting these limits, you can refer to the [Limits UI](/docs/data-apis/manage-data/view-system-limits/#limits-ui).

## How trace data is structured [#trace-structure]

Expand Down
Loading