resourceName as the label. You can click any custom event to see its full details, including parameters, response, and message. If isError is true, the timeline styles the event as an error.
Publishing events
Aftertrack(), publishCustomEvent sends an event for a tracked server. Its first argument is the tracked server instance:
sessionId (session_id in Python). A tracked server can serve many tasks at once, so AgentCat cannot know by itself which session the event belongs to. The Rust SDK can also publish from inside a tool call, in the session of that call: see the Rust reference.
Using a session ID
If you know theses_ ID of a session instead of the server instance, you can pass it as a string. AgentCat uses the string as the session ID of the event, unchanged:
publishCustomEvent reference
Event data
All fields are optional. A call with only the server and the project ID records a minimal custom event.
You can also add metadata to every tool-call event that AgentCat captures: see Event Tags & Properties.