Every action on the Traces page under Performance now has a logbook. One logbook holds the notes for all traces of an action. Traces expire, but notes stay with the action.
Open an action from the Traces page and add a note in the Logbook section of its Summary tab. Notes support Markdown, and you can edit, pin, and delete them. The pinned note shows first. The Logbook tab shows the full logbook on its own page.
Unlike a performance incident's logbook, whose notes have now moved to the trace logbook, our new trace logbook holds notes only. It does not record state changes or link GitHub issues.
Notes on performance incidents now live in this logbook too. A performance incident's Summary and Logbook tabs link to the action's trace page. They keep showing the incident's activity, such as state changes. Existing notes are copied over, so they stay available after the incident closes and its traces expire.
If you use the AppSignal MCP server, the manage_incident_note tool is now manage_note. It adds and edits notes on incidents by number, and on performance trace actions by namespace and action name. The old tool name keeps working.
Read the trace page docs for what each trace shows. That page is also where distributed tracing shows its service map and timeline. Distributed tracing is in beta as part of AppSignal Labs.
Tell us what you think of trace logbooks in our Discord channel.
