truefoundry-logs（truefoundry 日志）

Routing note: For ambiguous user intents, use the shared clarification templates in references/intent-clarification.md.

Logs

View and download application and job logs from TrueFoundry.

Scope

View, download, and search application and job logs from TrueFoundry. Useful for debugging deployments, checking startup output, and finding errors.

Download Logs

Security: Log output may contain sensitive data (secrets, tokens, PII). Do not forward raw logs to external services or include them in responses without reviewing for sensitive content first.

When using direct API, set TFY_API_SH to the full path of this skill's scripts/tfy-api.sh. See references/tfy-api-setup.md for paths per agent.

Via Tool Call

tfy_logs_download(payload={
    "workspace_id": "ws-id",
    "application_fqn": "app-fqn",
    "start_ts": "2026-02-10T00:00:00Z",
    "end_ts": "2026-02-10T23:59:59Z"
})

Via Direct API

# Set the path to tfy-api.sh for your agent (example for Claude Code):
TFY_API_SH=~/.claude/skills/truefoundry-logs/scripts/tfy-api.sh

# Download logs for an app in a workspace
$TFY_API_SH GET '/api/svc/v1/logs/WORKSPACE_ID/download?applicationFqn=APP_FQN&startTs=START&endTs=END'

# With search filter
$TFY_API_SH GET '/api/svc/v1/logs/WORKSPACE_ID/download?applicationId=APP_ID&searchString=error&searchType=contains'

Parameters

Presenting Logs

Show logs in chronological order. For long output, show the last N lines or summarize errors:

Logs for tfy-tool-server (last 20 lines):
2026-02-10 14:30:01 INFO  Server starting on port 8000
2026-02-10 14:30:02 INFO  Tools endpoint ready at /tools
2026-02-10 14:30:05 INFO  Health check: OK

<success_criteria>

Success Criteria

• The user can see recent logs for their application or job in chronological order
• Error patterns in the logs are identified and highlighted with suggested fixes
• The agent has filtered logs by the correct time range, application, and search terms
• The user understands why their application failed or what its current behavior is
• Log output is presented concisely, summarizing long output rather than dumping raw text

</success_criteria>

Composability

• Find app first: Use applications skill to get app ID or FQN
• Find workspace: Use workspaces skill to get workspace ID
• After deploy: Check logs to verify the app started
• Debug failures: Download logs with searchString=error

Error Handling

Missing workspace_id

workspace_id is required for log downloads.
Use the workspaces skill to find your workspace ID.

No Logs Found

No logs found for the given filters. Check:
- Time range is correct
- Application ID/FQN is correct
- The app has actually run during this period

Permission Denied

Cannot access logs. Check your API key permissions for this workspace.