Solution skill
Mezmo cost controls: exclusion rules, usage quotas, and archiving before retention expires
Complete solution
Shows how to fix mezmo cost controls: exclusion rules, usage quotas, and archiving before retention expires. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Set up exclusion rules and a usage quota before shipping production volume, not after the first bill: pair hard quota limits with exclusion rules that drop the noisy-but-useless lines while keeping errors.
Steps
- Set up exclusion rules and a usage quota before shipping production volume, not after the first bill: pair hard quota limits with exclusion rules that drop the noisy-but-useless lines while keeping errors. Turn on index rate alerts so volume spikes page you. If you need history past your plan's retention, enable archiving to your own S3 bucket early so nothing is lost.
When to use
You are seeing this: Turn on index rate alerts so volume spikes page you. Use this skill when you run into "Mezmo cost controls: exclusion rules, usage quotas, and archiving before retention expires".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Mezmo's quick-start guide documents the cost-control stack: exclusion rules filter out log data you do not need to store, usage quotas set hard and soft limits on ingestion with extra exclusion rules so you do not blow the budget, and index rate alerts use historical trends to flag unexpected volume spikes. Retention depends on the plan (the free trial stores logs for 14 days), and archiving exports data to external storage like S3 once retention concludes, with data restoration bringing it back into the UI.
Verified resolution: Set up exclusion rules and a usage quota before shipping production volume, not after the first bill: pair hard quota limits with exclusion rules that drop the noisy-but-useless lines while keeping errors. Turn on index rate alerts so volume spikes page you. If you need history past your plan's retention, enable archiving to your own S3 bucket early so nothing is lost.
Source URL: https://github.com/mezmo/documentation/blob/HEAD/docs/mezmo-quick-start-guide.mdx
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
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_Tk2DMJCxfiX2FvJq_0zYhg" 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 cost controls: exclusion rules, usage quotas, and archiving before retention expires <span>— Vectle</span></a>