正在加载视频...

视频加载失败

Today we're launching sensitive data redaction in Mastra observability! Automatically strip out your users’ PII from agent traces:

11,577 次观看 • 2 个月前 •via X (Twitter)

19 条评论

Sam Bhagwat 的头像
Sam Bhagwat2 个月前

𝚂𝚎𝚗𝚜𝚒𝚝𝚒𝚟𝚎𝙳𝚊𝚝𝚊𝙵𝚒𝚕𝚝𝚎𝚛 is enabled by default and you can customize fields. Here's the blog post:

Gautam Paranjape 的头像
Gautam Paranjape2 个月前

amazing! definitely really valuable

Sam Bhagwat 的头像
Sam Bhagwat2 个月前

yeah a really useful implementation of our processor api I think

Bob Remeika 的头像
Bob Remeika2 个月前

🚢🚢🚢

Benjamin Laval 的头像
Benjamin Laval2 个月前

awesome

Sam Bhagwat 的头像
Sam Bhagwat2 个月前

Thanks!

Mustafa Elsayed 的头像
Mustafa Elsayed2 个月前

Hi @calcsam I am using mastra with Pg as a store and memory, and noticed a delay about 3 seconds when connecting with PG, Is there anything that might produce such effect so I can revisit and enhance. Thanks

Brennan McEachran 👨‍🚀 的头像
Brennan McEachran 👨‍🚀2 个月前

Oft. i see PII redaction maintaining some traceability. Like, instead of "*" it's [EMAIL_1] Wonder how this will effect things like traces -> dataset -> evals

Sam Bhagwat 的头像
Sam Bhagwat2 个月前

this is a good point. pinging Eric on our team who shipped this

Brennan McEachran 👨‍🚀 的头像
Brennan McEachran 👨‍🚀2 个月前

I think my bias is coming from being exposed to this Which i think is a small model for this task

Sam Bhagwat 的头像
Sam Bhagwat2 个月前

yeah eric and i talked about this and it makes a lot of sense to both of us. will be working on it

Brennan McEachran 👨‍🚀 的头像
Brennan McEachran 👨‍🚀2 个月前

Appreciate you two

Dan Mullaney 的头像
Dan Mullaney2 个月前

PII redaction in traces is the compliance win, but the same trace-level visibility is what most teams are still missing on the cost side. If you can strip a field out of every agent trace automatically, you can just as easily tag every trace with what it cost to produce. Is cost attribution on the observability roadmap too, or does Mastra expect teams to bolt that on separately?

Sam Bhagwat 的头像
Sam Bhagwat2 个月前

we already have that

Dan Mullaney 的头像
Dan Mullaney2 个月前

Good to hear it's already there. Is it opt-in per project or on by default, and does it break down to the step or tool-call level, or just the trace as a whole? That granularity is usually the difference between a nice dashboard and something people actually use to make decisions.

anirudh 的头像
anirudh2 个月前

cool! didn't SensitiveDataFilter exist before too? what's new in this release 👀

Sam Bhagwat 的头像
Sam Bhagwat2 个月前

yeah, but we never actually announced it lol

Boring Automations 的头像
Boring Automations2 个月前

@mastra Yes having placeholders for redacted inputs is useful for maintaining context, for the agent receiving the user prompt and the downstream processes (eg. Observability, updating evals from real traces)

Praveen Yadav 的头像
Praveen Yadav2 个月前

What we use for redaction?

相关视频