Immutable solution version
Mezmo UI exclusion rules apply after ingestion, filter at the agent instead
Complete solution
Mezmo UI exclusion rules apply after ingestion, filter at the agent instead: Do not rely on UI exclusion rules to control data egress or keep sensitive logs in house: move include/exclude regex rules and redaction to the agent config so unwanted lines never leave your systems.
Do not rely on UI exclusion rules to control data egress or keep sensitive logs in house: move include/exclude regex rules and redaction to the agent config so unwanted lines never leave your systems. Use redaction templates for common PII patterns rather than trying to exclude everything after the fact. Re-check both the agent rules and the UI rules after upgrades, since the two layers behave differently.
Context: Mezmo's Agent 3.2 announcement documents a cost and privacy trap in UI-side exclusion rules. Exclusion rules configured in the Mezmo UI are applied only after ingestion, which means customers still pay egress for the unneeded log data, and logs containing PII can leave their system of origin before being excluded. The 3.2 agent instead supports inclusion and exclusion rules plus redaction via regex patterns applied at the agent, so filtered logs never leave the host.
Matched source
Source: Published skill Original query: "Mezmo UI exclusion rules apply after ingestion, filter at the agent instead" Key terms: after, agent, apply, exclusion, filter, ingestion, instead, mezmo, rules
Evidence
Source: Mezmo's Agent 3.2 announcement documents a cost and privacy trap in UI-side exclusion rules. Exclusion rules configured in the Mezmo UI are applied only after ingestion, which means customers still pay egress for the unneeded log data, and logs containing PII can leave their system of origin before being excluded. The 3.2 agent instead supports inclusion and exclusion rules plus redaction via regex patterns applied at the agent, so filtered logs never leave the host.
Verified resolution: Do not rely on UI exclusion rules to control data egress or keep sensitive logs in house: move include/exclude regex rules and redaction to the agent config so unwanted lines never leave your systems. Use redaction templates for common PII patterns rather than trying to exclude everything after the fact. Re-check both the agent rules and the UI rules after upgrades, since the two layers behave differently.
Source URL: https://www.mezmo.com/blog/announcing-logdna-agent-3-2-ga
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_z44ZNO3WaPR9KCTruuGU4w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Mezmo UI exclusion rules apply after ingestion, filter at the agent instead <span>— Vectle</span></a>