Conversation
Metric Rules match expressions and variable extractions now also support colon (:) as a segment delimiter, alongside dot, gated behind metrics.rules.parser.enable.extended.delimiters (SUMO-292913). Useful for colon-separated identifiers like AWS ARNs. Adds a note that a colon-delimited expression matching nothing may mean the flag isn't enabled yet for the account.
Microsoft Manual of Style outranks Chicago in our style guide's reference precedence, and Microsoft recommends against suspended compound modifiers outside space-constrained contexts. Spells out "dot-delimited or colon-delimited" in full instead of "dot- or colon-delimited", and adds a Word List entry so this doesn't need re-litigating.
- metric-rules-editor.md: "a match expression can be a dot-delimited or colon-delimited string" (was "one or more ... string", singular/plural mismatch). - word-list.md: closing period now inside the quote, matching the first example and the file's existing convention.
…g is GA Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
kimsauce
left a comment
kimsauce
left a comment
There was a problem hiding this comment.
Reviewed the colon-delimiter docs change. Content is accurate and the anchor/link updates are consistent. A few small things inline: one consistency question on the non-_rawName bullet, a heads-up on the changed heading anchor, and an em dash in the new Word List entry. — via Claude Code
| 1. In the **Define variables** section of the page, for each tag you want to apply to matching metrics, enter a meaningful tag name in the **Variable name** field on the left. In the **Tag sequence** field, assign a variable to the tag. There are two different formats for specifying the Tag Sequence. | ||
| * To pull a tag from a dot-delimited string in the metric's `_rawName` field, use `$_1` to extract the first segment of the string, `$_2` to extract the second segment of the string, and so on. For more information, see [Extracting variables from a dot-delimited match expression](#extract-variables-from-a-dot-delimited-match-expression). | ||
| * To pull a tag from a dot-delimited or colon-delimited string in the metric's `_rawName` field, use `$_1` to extract the first segment of the string, `$_2` to extract the second segment of the string, and so on. For more information, see [Extracting variables from a dot-delimited or colon-delimited match expression](#extract-variables-from-a-dot-delimited-or-colon-delimited-match-expression). | ||
| * To pull a tag from a dot-delimited string in metric field other than `_rawName` field, use `$FieldName._1` to extract the first segment of the string, `$FieldName._2` to extract the second segment of the string, and so on. For more information, see [Extracting variables from a key-value pair match expression](#extract-variables-from-a-key-value-pair-match-expression). |
There was a problem hiding this comment.
This second bullet (non-_rawName fields, $FieldName._1) still says "dot-delimited" only. Does the colon delimiter apply here too, or is it _rawName-only? Worth making it match the bullet above either way. — via Claude Code
| A metric match expression defines the scope of the rule. Put another way, the match expression specifies the metrics to which the tags (defined by variable extraction) will be applied. | ||
|
|
||
| ### Dot-delimited match expressions | ||
| ### Dot-delimited or colon-delimited match expressions |
There was a problem hiding this comment.
Renaming this heading changes its anchor to #dot-delimited-or-colon-delimited-match-expressions. Internal refs are updated, but any external bookmarks/inbound links to #dot-delimited-match-expressions will break. Just a heads-up. — via Claude Code
| ### Dot-delimited or colon-delimited match expressions | ||
|
|
||
| A match expression can be one or more dot-delimited string, like this: `collectd.*.*.*.*`, which matches all Graphite metrics that have five segments in the string, where the value of the first segment is `collectd`. | ||
| A match expression can be a dot-delimited or colon-delimited string. For example, `collectd.*.*.*.*` matches all Graphite metrics that have five segments in the string, where the value of the first segment is `collectd`. Colon-delimited match expressions work the same way, and are useful for colon-separated identifiers such as AWS ARNs, for example: `arn:aws:bedrock-agentcore:*:*:*`. |
There was a problem hiding this comment.
arn:aws:bedrock-agentcore:*:*:* with $_4 = region checks out (arn / aws / service / region / account / resource). "Colon-delimited match expressions work the same way" slightly restates the first sentence; could drop it. — via Claude Code
|
|
||
| **Sumo Logic**. For all references, always use "Sumo Logic," never "Sumo" alone, including in the possessive. This helps our SEO, which is essential for a SaaS offering. To be more conversational, "we" is also fine. | ||
|
|
||
| **Suspended hyphens**. Avoid these in body text — spell out both compound modifiers in full: "dot-delimited or colon-delimited," not "dot- or colon-delimited." |
There was a problem hiding this comment.
Em dash here, and the Em dash entry above says we avoid them. Suggest: Avoid these in body text. Spell out both compound modifiers in full: "dot-delimited or colon-delimited," not "dot- or colon-delimited." — via Claude Code
3 participants
Purpose of this pull request
Documents the colon-delimiter support for Metric Rules match expressions and variable extractions, per SUMO-292913 (enabling the
metrics.rules.parser.enable.extended.delimitersflag).Verified via
yarn build(no broken links/anchors).Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1852