Mezmo

09/24/2026

That’s a wrap on DevOpsDays Rockies 🏔️

Great couple of days connecting with the community, talking all things AI, and sharing what we’re building with AURA.

Thanks to everyone who connected with our team and to DevOpsDays Rockies for having us!

09/09/2026

Got something weird happening with your agents? Bring it to Office Hours. 💜

Bugs, broken workflows, unexpected behavior, half-built ideas, or something you just can’t quite explain. AURA Office Hours is an open space to troubleshoot, ask questions, and build alongside the team.

No slides. No sales pitch. Just show up with what you’re working on.

📅 Today (& every Wednesday) at 11 AM PDT
🔗 Join us: https://lnkd.in/gRFxky5v

09/03/2026

3 am. Alert fires. You wake up, VPN in, squint at a laptop, and ask the same three questions every on-call human has asked since the dawn of PagerDuty.

What changed? What else broke? Haven't we seen this before?

Cute ritual. Also a waste of your first ten minutes.

AI Investigations means AURA is already digging by the time you find your glasses. Evidence, hypothesis, receipts, all waiting for you to judge.

Not a chatbot. Not a spinner. An investigation with a head start.

Stop waking up to a blank page. Wake up to a lead. 👉 https://www.mezmo.com/blog/ai-investigations-automated-root-cause-analysis

A Mezmo AI Investigation is a root cause analysis record AURA produces when a Pipeline node alert fires, with evidence, a confidence score, and a root cause.

09/01/2026

Bring the weird things. We mean it. 💜

AURA Office Hours is your weekly space to bring the bugs, broken workflows, strange agent behavior, half-baked ideas, and “why is it doing that?” moments.

No deck. No pitch. Just engineers, AURA, and whatever weird thing you’re working through.

📅 Wednesdays at 11 AM PDT
🔗 Join us: https://mezmo.zoom.us/meetings/97561758615/invitations?signature=hsOFho_O3R7IZxXzyPM2rNjm33pQEOEede-oUlFTFC8

08/31/2026

Day 31 of 31 days of ✨AURA✨: The last day of the series, and a problem every AWS team has hit.

Greg Janco gives AURA a Lambda function that can't access an S3 bucket due to a permissions issue. AURA finds the missing piece (list bucket permission) and hands back the exact minimum policy needed to fix it. Add it to the role, rerun the function, and all 11 files come back successfully.

Simple example, same pattern that scales to bigger AWS problems, and to multiple AURA agents working together across your environment.

🎬 Watch day 31: https://www.mezmo.com/videos/s3-access-denied-ai-sre-agent-debugs-lambda-permissions

08/30/2026

Day 30 of 31 days of ✨AURA✨: Approving an action shouldn't mean the request runs with the agent's permissions instead of yours.

Mike Shearer shows how AURA's human-in-the-loop approvals forward identity, not just a yes or no. When a fake key is used to approve creating a pipeline, the downstream service denies it anyway. Approve with a real key, and the request runs under the approver's actual identity and permissions, tracked all the way through.

Built for privileged workflows where who approved something matters just as much as whether it got approved.

🎬 Watch day 30: https://www.mezmo.com/videos/aura-approval-workflow-identity-forwarding-to-mcp-servers

08/29/2026

Day 29 of 31 days of ✨AURA✨: We keep your keys out of the agent entirely.

Mike Shearer shows how AURA handles authentication without hardcoding secrets into your config. Instead of storing keys directly, AURA can forward headers from the request itself, mapping something like an incoming authorization header straight to the downstream MCP server at call time.

No headers, no access. Pass them, and AURA authenticates as you, with your permissions.

Built for multi-tenant setups and identity forwarding, so different users get different access to different services, exactly as it should be.

🎬 Watch day 29: https://www.mezmo.com/videos/mcp-authentication-by-header-for-an-ai-sre-agent-aura

08/28/2026

Day 28 of 31 days of ✨AURA✨: We showed AURA auto-investigating PagerDuty incidents. Here's what's actually running under the hood.

Today we go behind the scenes on the bridge connecting Grafana, PagerDuty, Slack, and AURA, how an alert turns into an agent talking (and asking for approval) right in your incident channel. Built in about an hour, with Claude doing the coding.

🎬 Watch day 28: https://www.mezmo.com/videos/ai-sre-agent-behind-the-scenes-wiring-aura-into-slack

08/27/2026

Day 27 of 31 days of ✨AURA✨: Nobody wants to hand-query system tables at 3 a.m.

Kwabena points AURA at a self-hosted, multi-replica ClickHouse cluster and lets three specialist workers investigate in parallel: workload, storage, and replication.

They inspect query activity, parts, merges, mutations, and replica health across the cluster, then pull the findings together into a report.

Every worker is read-only. AURA can query and recommend, but it cannot drop tables or make changes.

A Python job runs the check every 10 minutes and sends a trimmed report to Slack.

Read-only by design. On a schedule you set.

🎬 Watch day 27: https://www.mezmo.com/videos/ai-sre-agent-monitors-clickhouse-and-posts-to-slack-aura

08/26/2026

Day 26 of 31 days of ✨AURA✨: 3 am. The pager fires. The runbook describes a service that shipped three versions ago.

Runbooks go stale because clusters change faster than docs.

Today we show AURA closing that gap: finding the drift, drafting real runbooks from live cluster state, and flagging an alerting gap nobody caught, all as proposed PRs a human reviews before anything merges.

🎬 Watch day 26: https://www.mezmo.com/videos/ai-sre-agent-audits-kubernetes-runbook-coverage-aura