Product update: Logs - #486
Conversation
✅ Deploy Preview for bump-content-hub ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| MCP servers now keep a persistent history of every tool call: which tool was invoked, when, from where, whether it succeeded, and how long it took. Where debug sessions only cover a short live window, logs stick around. Use them to see how a server is actually used, and to investigate an issue after it happened. | ||
|
|
||
| You can also surface custom execution data by defining custom analytics in your workflow definition document. Runtime expressions let you pick the inputs, outputs or configuration values, and inspect them without opening a debug session. Authentication data is always excluded. |
There was a problem hiding this comment.
Not sure if it's the right place in a product update but I'll tell the reader not to send PPI information.
I like how appsignal does it:
You can send virtually any data point to AppSignal in a tag, so long as it's not Private Personal Information (PPI). Private personal information includes things like names, emails, and telephone numbers.
There was a problem hiding this comment.
That's important, but I'm not sure it's relevant in a product update, as we already say it in the help center. Do you think simply mentioning that authentication can't be logged is enough?
paulRbr
left a comment
There was a problem hiding this comment.
besides the warning about not sending PPI (or secret/private info) in custom anaytics, LGTM!
No description provided.