truefoundry-ai-monitoring
Routing note: For ambiguous user intents, use the shared clarification templates in references/intent-clarification.md.
AI Monitoring
Query AI Gateway request traces, costs, latency, errors, and token usage via the spans query API.
When to Use
Investigate gateway traffic: recent requests, cost breakdowns, error rates, model usage, per-user activity, MCP tool calls, or latency analysis.
When NOT to Use
- User wants to instrument their own application with tracing -> prefer
tracingskill (this skill is for querying existing gateway traces, not adding instrumentation) - User wants to configure gateway models, routing, or rate limits -> prefer
ai-gatewayskill - User wants to view application container logs -> prefer
logsskill - User wants to check platform connectivity -> prefer
statusskill
More from truefoundry/tfy-gateway-skills
truefoundry-access-control
Manages TrueFoundry roles, teams, and collaborators. Create custom roles, organize users into teams, and grant access to resources. Use when managing permissions, creating teams, or adding collaborators.
2ai-monitoring
Monitors AI Gateway traffic, costs, latency, errors, and token usage by querying request traces via the spans query API.
2truefoundry-access-tokens
Manages TrueFoundry personal access tokens (PATs). List, create, and delete tokens for API auth, CI/CD, and gateway access.
2truefoundry-ai-gateway
Configures TrueFoundry AI Gateway for unified OpenAI-compatible LLM access. Covers auth (PAT/VAT), model routing, rate limiting, and budget controls.
2truefoundry-status
Checks TrueFoundry connection status and verifies credentials (TFY_BASE_URL/TFY_HOST, TFY_API_KEY). Used as a preflight check before any TrueFoundry operation.
2truefoundry-mcp-servers
Registers MCP servers with TrueFoundry for discovery and access control. Supports remote servers, virtual (composite) servers, and OpenAPI-to-MCP wrapping. Use when adding, listing, or managing MCP server registrations.
2