[pull] master from DataDog:master - #1106
Merged
Merged
Conversation
… page (#39386) * RUM: document exclusion filters and restructure the retention filters page Exclusion filters are a new type of filter, evaluated between the permanent and the custom retention filters. An event matching an exclusion filter is not evaluated against the custom retention filters, so it can never be the reason its session is retained. Because there are now three types of filters, the page is reorganized so that each type is documented in its own section: - New "Types of filters" section: the path an event takes through the three types, and a table contrasting what a match does in each case. Exclusion filters are event-scoped; retention filters are session-scoped. This is the distinction most likely to be misread. - "Creating a retention filter", "Modifying filters" and "Excluding sessions using retention filters" are now subsections of a new "Custom retention filters" section. Heading text is unchanged so existing deep links still resolve. - New "Exclusion filters" section (Preview), covering the event type + query model, "All events" targeting, order-independence, and the predefined filter for errors ignored in Error Tracking. - "Excluding sessions using retention filters" is rewritten: in-query exclusions are scoped to a single filter, and exclusion filters are the way to exclude across the whole configuration. - "How retention filters work with replays" moves below the filter types, next to the other cross-cutting sections. Also updates the best practices guide to point at exclusion filters, and fixes its link to retention_filters/#logic, an anchor that does not exist on the page (now #how-it-works). Screenshots still show the previous UI and are replaced before merge. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * RUM: address review feedback on the filters restructure - Overview: how to reach the Retention Filters page, including the new Settings entry point, instead of repeating it in the creation steps. - Types of filters: drop the billing claim from the table (it does not hold for the forced replay permanent filter) and the scope column and paragraph; the event-scope point stays in the Exclusion filters callout. - Exclusion filters: tighter definition, no cross-product mention. - "Creating a filter" and "Modifying filters" are now standalone sections covering both custom retention and exclusion filters. - Excluding sessions: the minimum retention rate is 0.1%, not 1%. - Error Tracking filter: cannot be edited either. - Quotas link now reads "Retention Quotas", matching the nav entry. - Link the mobile conditional recording APIs. - Drop the cross-product note about filter ordering. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * RUM: lead with the Settings shortcut in the retention filters overview Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * RUM: group the filter configuration steps under a Setup section Adds a Setup section holding the page access instructions, with "Creating a filter", "Modifying filters" and "Capping retention with quotas" as its subsections, matching how other RUM pages are laid out. Exclusion filters now come before custom retention filters, so the sections follow the order in which an event is evaluated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * RUM: drop the exclusion filter note from How it works Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * RUM: trim the out-of-order evaluation note Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * RUM: tighten the logical flow bullets in How it works Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * RUM: trim the notes in How it works * RUM: shorten the retention decision wording * RUM: add the new filter group screenshots * RUM: link the exclusion filters preview signup form * RUM: apply review suggestions on the filters page * RUM: rename the in-query exclusion section to avoid confusion with exclusion filters --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )