Загрузка видео...

Не удалось загрузить видео

На главную

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?

Похожие видео