Skip to main content
Log alerts tell you when something shows up in a container’s logs, or when logs that should keep coming stop. You create rules per container, receive alerts in the console, by email, and on the desktop, and can also send them to external channels (Slack, Discord, and webhooks).
Rules count only log lines that arrive after you save them. Lines that appeared before the rule was saved never trigger it.

Create a Rule

  1. Open the container’s Runtime Logs page.
  2. Click Log alerts above the left panel. The rule list opens on the right.
  3. Click Add rule, set the pattern, the condition, and the notification frequency, then click Create.
You can also start from what you are looking at. Type a search in the log search box and click the bell icon at its right end (Create an alert from this search). The rule dialog opens with your search text and search mode already filled in. A new or edited rule can take up to about 15 seconds to take effect.

Pattern

  • Length: Patterns can be up to 500 characters.
  • Case: Rules created with Add rule ignore case. Rules created from the search-box bell are case-sensitive, like the log search. Start a regex with (?i) to ignore case.
  • Scope: Lines from every replica of the container are counted together.
  • Excluded lines: Health-check and metrics request lines (GET …/health, GET …/metrics) are not counted. ANSI color codes are stripped before matching.

Conditions

How “It stops appearing” is evaluated

Because this condition watches for lines that do not arrive, a few rules apply.
  • Only while running: It is evaluated only while the container is running or unhealthy. It never fires while the container is stopped or deploying.
  • After one full window: It alerts only after watching for at least N minutes since the rule was created, edited, or turned back on, or since the container started running. Checks run every minute, so an alert can arrive 1–2 minutes late.
  • Only when logs are arriving: If not a single line from the container has been collected since watching started, it does not alert — a broken collection path should not be reported as “logs stopped.” Health-check and metrics lines count as proof that logs are being collected.
Health-check and metrics lines are excluded from pattern matching, so an “It stops appearing” rule on a server with no traffic can fire even when the server is healthy.

Notification Frequency

This sets how often to notify again while the condition keeps matching. A rule alerts at most once per interval. Turning a rule back on, or changing its pattern or condition, starts counting from scratch regardless of when it last alerted.

Common Patterns

The rule dialog offers common patterns you can start from. All of them ignore case.
  • Combine patterns: Patterns with the same default condition can be picked together and combined into one rule. The combined pattern becomes a regex and cannot exceed 500 characters. Logs stopped cannot be combined with other patterns.
  • Suggested rules: Above the rule list, patterns that actually appeared in the last 24 hours of logs are shown with their counts. Click Create to turn one into a rule.

Recipients

  • Only Organization Owners and admins can choose recipients. Rules created by members always notify Me.
  • Email follows each recipient’s own notification settings, where it can be turned off under Log alert rules.
  • Under Also send to external channels, each rule can pick up to 10 of the organization’s Slack, Discord, and webhook channels. Each alert is sent once to every selected channel.

What an Alert Looks Like

  • Console notification: Titled “Log alert fired in container ''”, with the rule name, the condition, and up to 5 matching lines.
  • Email: Contains the container, rule, condition, and matching lines, sent in Korean or English based on the organization’s region.
  • View logs: View logs on an alert opens the logs of the replica that matched last, already searched with the rule’s pattern. “It stops appearing” alerts open the log view without a search.
  • History: On the Notifications page, filter History to Log alerts. View alert history in the rule list shows log alerts for that container only.

Manage Rules

The rule list shows each rule’s condition, frequency, recipients, number of external channels, and when it last alerted and last matched.
  • On/off: Use the switch to pause a rule. Rules that are off are marked Off.
  • Edit and delete: Use the ⋯ menu on a rule. Deleted rules cannot be restored.
  • Permissions: Only the rule’s creator, or an Organization Owner or admin, can change or delete a rule.

Limits

Monitoring

Watch live logs and logs per replica.

External Channels

Send log alerts to Slack, Discord, and webhooks.