maple-agent-tracing-ag…
Trace Agno agents with Maple: installs the OpenInference Agno instrumentor with an OTLP exporter and GenAI attributes, and sets…
Identify signed-in users in an app that already sends telemetry to Maple, so each person gets a page on Maple's Users page with their sessions, traces, logs, errors and events. Triggers on requests like 'identify users for Maple', 'fill the Maple Users page', 'add user.id to my
Claude Code
$ npx -y skills add mapletechlabs/maple --skill maple-identify-users --agent claude-code
Codex
$ npx skills add mapletechlabs/maple --skill maple-identify-users -a codex -y
Cursor
$ npx skills add mapletechlabs/maple --skill maple-identify-users -a cursor -y
Gemini CLI
$ npx skills add mapletechlabs/maple --skill maple-identify-users -a gemini-cli -y
GitHub Copilot
$ npx skills add mapletechlabs/maple --skill maple-identify-users -a github-copilot -y
OpenCode
$ npx skills add mapletechlabs/maple --skill maple-identify-users -a opencode -y
Windsurf
$ npx skills add mapletechlabs/maple --skill maple-identify-users -a windsurf -y
name: maple-identify-users description: "Identify signed-in users in an app that already sends telemetry to Maple, so each person gets a page on Maple's Users page with their sessions, traces, logs, errors and events. Triggers on requests like 'identify users for Maple', 'fill the Maple Users page', 'add user.id to my spans', 'tie telemetry to users'."
Maple's Users page lists everyone your telemetry names. A person shows up once any of these carry their id:
This skill assumes the app already exports OpenTelemetry to Maple. If nothing reaches Maple yet, run the onboarding skill first: `https://maple.dev/SKILL.md`.
Search the repo for the places that resolve the signed-in user: the auth provider's client hook or session callback in the frontend (Clerk, Auth.js, Supabase, Firebase, Auth0, a custom `/me` call), and the auth middleware, request guard or session lookup in each backend service. Identify at those points only, never in individual handlers.
Use the app's stable user id (the database or auth provider id). Never an email or name as the id.
With `@maple-dev/browser`, call `identify` right after sign-in resolves and clear it on sign-out:
import { MapleBrowser } from "@maple-dev/browser"
// after sign-in, and on page load when a session already exists
MapleBrowser.identify({
id: user.id,
email: user.email, // optional
username: user.username, // optional
groupId: org.id, // optional: the company, team or workspace
groupName: org.name, // optional
})
// on sign-out
MapleBrowser.identify(null)If the user is known when `MapleBrowser.init` runs, pass the same object as `user` in `init()` instead. Each `identify` call replaces the identity; it does not merge.
With `@maple-dev/effect-sdk/client`, use `identify(user.id)` and `clearIdentity()` from `@maple-dev/effect-sdk/client`.
`groupId` and `groupName` are what the Users page groups by. Set them whenever the app has an organization, team or workspace concept.
In the auth middleware of each service, once the user is resolved, set the attributes on the **request's root (server) span**, the one the HTTP instrumentation created for the request, not a child span:
import { trace } from "@opentelemetry/api"
const span = trace.getActiveSpan()
span?.setAttribute("user.id", user.id)
span?.setAttribute("user.email", user.email) // optional
span?.setAttribute("user.name", user.name) // optionalThe same keys in other languages: Python `span.set_attribute("user.id", ...)`, Go `span.SetAttributes(attribute.String("user.id", ...))`, Java `Span.current().setAttribute("user.id", ...)`, Rust `tracing::Span::current().record("user.id", ...)` (declare the field on the span). In Effect, `Effect.annotateCurrentSpan("user.id", user.id)` inside the request handler's span.
If the app logs through OpenTelemetry, add `user.id` to the log context the same way (structured field or log attribute), so log lines reach the same user page.
Do not put passwords, tokens or other secrets in attributes. Only send `user.email` and `user.name` if the app's privacy policy allows it; the id alone is enough for the page to work.
1. Run the app, sign in, click around. 2. Open `https://app.maple.dev/users` (EU: `https://app.eu.maple.dev/users`). The user should appear within a minute, with requests and sessions counted. 3. If only some signals show up, check the root server span of a request in the trace view for `user.id`, and check a browser session on the Replays page for the user columns.
Report back which files you changed, which services now set `user.id`, and anything you could not identify (for example a service with no auth context).
Trace Agno agents with Maple: installs the OpenInference Agno instrumentor with an OTLP exporter and GenAI attributes, and sets…
Trace Claude Agent SDK agents (TypeScript and Python) and Claude Code CLI sessions with Maple: configure Claude Code's built-in…
Trace Cloudflare Agents SDK agents (AIChatAgent, Agent on Durable Objects, npm `agents` / `@cloudflare/ai-chat`) with Maple:…
Trace CrewAI crews and flows with Maple: OpenInference CrewAI instrumentor plus the model-SDK instrumentor, GenAI dual-write, one…
Trace DSPy programs and ReAct agents with Maple: OpenInference DSPy instrumentor with GenAI dual-write, a DSPy callback for…
Trace eve agents (Vercel's eve framework, npm `eve`) with Maple: add one OpenTelemetry destination file under…
Kubeshark installation and deployment skill. Use this skill whenever the user wants to install Kubeshark, deploy Kubeshark to a…
Call the user on the phone for real-time voice conversations. Use this when you need input, want to report on completed work, or…