Skip to main content

LogBlocks

LogBlocks let you selectively block log events from being ingested and stored. Use them to reduce log volume and costs by filtering out noisy, low-value, or sensitive log lines before they reach storage.

Log Block Rules list page

How It Works​

  1. Logs enter the Oodle ingestion pipeline.
  2. Each log event is evaluated against all active LogBlock rules in the pipeline.
  3. If the event matches a rule, it is discarded and never stored.
  4. Events that do not match any rule proceed to storage normally.

LogBlock rules take effect immediately — matching logs are dropped as soon as the rule is created.

Creating a LogBlock​

  1. Navigate to Logs → LogBlocks in the sidebar.
  2. Click Create LogBlock.
  3. Fill in the form:
    • Name — A descriptive name for the rule (e.g. "Drop debug logs from chatbot").
    • Filter — Use the log filter builder to define which logs to block. Filters support conditions like field equals, not equals, contains, regex, etc. You can combine multiple conditions with All (AND) or Any (OR) logic.
  4. Preview — When available, the preview section shows how the rule fits into the pipeline and displays a sample log that matches the filter so you can confirm the rule targets the right events.
  5. Click Save to activate the rule.
caution

LogBlock rules are permanent blockers — once a matching log is discarded, it cannot be recovered. Always preview matching logs before saving.

Managing LogBlocks​

The LogBlocks list page shows all configured rules:

ColumnDescription
NameThe rule name. Click to open the editor.
ActionsContext menu with Edit, Clone, and Delete options.
  • Search — Use the search bar to filter rules by name.
  • Bulk actions — Select multiple rules with checkboxes and delete them in one step.

Use Cases​

  • Drop debug logs from production services that generate high volume.
  • Filter health-check logs from load balancers that add noise without insight.
  • Remove sensitive data — Block logs containing PII before they are stored.
  • Cost control — Reduce ingested volume to stay within budget.

Best Practices​

  • Be specific with filters — Overly broad rules can accidentally block important logs.
  • Preview before saving — Always review the preview to verify the rule targets the correct logs.
  • Combine with LogTransforms — Use LogTransforms to restructure logs and LogBlocks to remove the ones you do not need at all.
  • Use descriptive names — Include the target service or log level in the rule name so others can understand it at a glance.

Support​

If you have any questions or need assistance, please contact us via our help chat app available on the Support link in the sidebar, or by reaching out to support@oodle.ai.