Skip to main content

Tags and automatic rules

Tags are colored, labeled markers you attach to issues so you can group, filter, and triage related errors. A tag can be applied two ways: manually, one issue at a time, or automatically, through a match-word rule that Log Lens evaluates for you.

What a tag looks like​

Every tag has a name, a color, and an icon.

FieldRules
NameRequired, trimmed, max 80 characters, must be unique
ColorSix-digit hex like #3b82f6 (stored lowercase)
IconLowercase slug: starts with a letter, then letters, digits, _ or -, up to 32 characters
Match wordOptional rule text, max 200 characters

Creating a tag with a duplicate name is rejected with "A tag with this name already exists."

Manual assignment​

You can attach or detach a tag on any issue directly. Manual assignments are recorded with the source manual and are yours to control - they are never removed by rule processing.

Automatic rules​

When a tag has a match word, Log Lens turns it into a rule. Every time rules run, the tag is applied to any issue whose title, sample message, or exception class contains that word:

title LIKE %word%  OR  sample_message LIKE %word%  OR  exception_class LIKE %word%

Matching is substring-based and case-insensitive. Only enabled rules are evaluated. Rule-applied tags carry the source rule.

Rules are re-run automatically whenever you create or update a tag.

Manual vs rule, and how they interact​

The source (manual or rule) matters when a tag is applied by both paths:

  • If a rule already tagged an issue and you assign the same tag manually, the assignment is upgraded to manual.
  • Editing a tag clears its existing rule assignments and re-applies the current rule - but any manual assignments stay untouched.

This means a manual choice always outranks automation: once you tag something by hand, changing or disabling the rule will not strip it away.

Deleting a tag​

Deleting a tag removes it along with its assignments and rule. Manual and rule assignments alike disappear.