Tag Rules Help

Tag Rules Back to Settings
Match

Rules match by record type, field/operator/value, and optional attribute key.

Assign

Matching records receive normalized key/value tags used in filtering and correlation.

Correlate

Tags can drive anomaly rules, notification conditions, and service ownership views.

Rule Basics
Tag rules evaluate ingest records and apply normalized key/value tags for filtering and correlation across logs, traces, errors, AI, and RUM.
Best Practices
  • Prefer stable tag keys that map to service ownership or failure domains.
  • Use regex sparingly and test against expected payload samples.
  • Avoid overlapping rules that set conflicting values for the same key.
  • Use explicit record type scope before broad all-type rules.
Example Rule Patterns
  • Service ownership: if service_name contains checkout -> team=payments
  • Environment flag: if attr.env equals prod -> env=production
  • Error family: if body matches timeout regex -> error_family=timeout
Rollout Checklist
  1. Create rule with a narrow service scope.
  2. Verify tag appears in recent records.
  3. Add notifications/anomaly logic that references the tag.
  4. Scale scope from one service to broader domains.
Legacy rules without ConditionsJson are auto-mapped into editable condition rows for compatibility.