Conversation
…on Rules Remove the 15-day retention and 15-day aggregate retention options, which are no longer available. Retention is now Do Not Store or 400 days, and aggregate retention is always 400 days. Update the intro, key facts, and examples to match. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…on change Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Reframe title as an update rather than a removal, open with "We're excited to announce," and condense the body to two sentences. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
kimsauce
left a comment
kimsauce
left a comment
There was a problem hiding this comment.
Inline comments below from a single-pass review. The change is scoped correctly (no other doc references the 15-day transformation-rule option), and the drive-by fixes are good catches: the "does not not appear" typo on line 44 and the "400 Days"/"15 Days" -> "400 days" casing normalization. Main items are the unaddressed impact on existing 15-day rules and the first example, which has become internally contradictory and largely redundant with the second.
— via Claude Code
|
|
||
| * A metrics transformation rule applies to metrics that match a selector that you define for the rule. You can check what metrics will be affected by entering the selector in a metric query tab. | ||
| * You can reduce the amount of time that Sumo Logic will retain metrics that match the rule selector. By default, Sumo Logic saves your metrics for 400 days. In a transformation rule, you can set the retention period for metrics that match the selector to 15 days. | ||
| * By default, Sumo Logic saves your metrics for 400 days. If you aggregate the metrics that match the rule selector, you can also choose to discard the raw metrics entirely by setting their retention to **Do Not Store**. |
There was a problem hiding this comment.
What happens to rules that already use 15-day retention: migrated to 400 days, or Do Not Store? Worth a line here or in the release note.
— via Claude Code
| Assume that the metrics you collect from your dev environment are of | ||
| no interest once they've been aggregated. You tag metrics from the dev | ||
| environment with a dimension whose key is “environment” and value is | ||
| “dev”. When you configure your rule: | ||
|
|
||
| 1. Selector. Enter: `environment=dev` | ||
| 1. Retention. Select ` days` from the pull-down list. | ||
| 1. Aggregate On. Add the dimensions you want to aggregate by, for example, `environment`. | ||
| 1. Retention. Select **Do Not Store**. | ||
| 1. Aggregate Retention. **400 days** (the only available option). | ||
|
|
||
| All metrics that match the selector `environment=dev` will be stored for 15 days, and then removed. They will not be aggregated, as aggregation is optional. In this case, we are simply using the transformation rule to control how long we want to retain the metrics. By default, Sumo Logic stores metrics for 400 days. A rule like this lets you reduce the metric retention period to 15 days. | ||
| All metrics that match the selector `environment=dev` are aggregated and the raw metrics are discarded, so you keep the aggregated trend data without paying to store 400 days of raw dev-environment metrics you have no interest in. |
There was a problem hiding this comment.
Intro says the dev metrics are of no interest once aggregated, but this line says you keep the aggregated trend data. And since Do Not Store now requires aggregation, this example duplicates the one below. Consider merging them.
— via Claude Code
|
|
||
| 1. Selector. Enter: `environment=dev` | ||
| 1. Retention. Select ` days` from the pull-down list. | ||
| 1. Aggregate On. Add the dimensions you want to aggregate by, for example, `environment`. |
There was a problem hiding this comment.
The selector already pins environment=dev, so aggregating on environment yields a single series. Use service or similar.
— via Claude Code
| ## Metrics transformation rule examples | ||
|
|
||
| ### Change metrics retention to 15 days | ||
| ### Discard metrics from development and test environments |
There was a problem hiding this comment.
Heading says "and test," but the example only shows environment=dev. Broaden it or drop "and test."
— via Claude Code
| hide_table_of_contents: true | ||
| --- | ||
|
|
||
| We're excited to announce updated retention options for Metrics Transformation Rules. Retention for matching metrics is now **Do Not Store** or **400 days**, and aggregate retention for aggregated metrics is now standardized to **400 days**. |
There was a problem hiding this comment.
Lowercase "metrics transformation rules" mid-sentence per the repo convention (cap only UI labels). Bold option names are fine.
— via Claude Code
|
|
||
| We're excited to announce updated retention options for Metrics Transformation Rules. Retention for matching metrics is now **Do Not Store** or **400 days**, and aggregate retention for aggregated metrics is now standardized to **400 days**. | ||
|
|
||
| [Learn more](/docs/metrics/metrics-transformation-rules/). |
There was a problem hiding this comment.
Recent *-manage.md notes keep [Learn more] inline at the end of the paragraph, not on its own line.
— via Claude Code
2 participants
Purpose of this pull request
This pull request removes the 15-day retention and 15-day aggregate retention options from Metrics Transformation Rules, since they're no longer available in the product. The available options are now:
Updated the intro use-case bullets, the "Key facts" section, the Retention and Aggregate Retention steps, and both walkthrough examples in
docs/metrics/metrics-transformation-rules.mdto match. The first example, previously "Change metrics retention to 15 days," is renamed to "Discard metrics from development and test environments" and now demonstrates the Do Not Store option instead.Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1870