b2c-logs_skill

Overview

This skill uses the b2c CLI to retrieve and monitor logs from Salesforce B2C Commerce instances. It provides agent-friendly, non-interactive log retrieval with structured JSON output and supports filtering by time, level, and text. Use it to fetch recent errors, search log messages, or tail logs in real time for human troubleshooting.

How this skill works

The skill runs b2c logs get to return recent entries and supports --json for structured results that include file, timestamp, level, message, and raw fields. It accepts filters such as --since (relative or ISO time), --level, --search, and --filter (log type) to narrow results, and it normalizes file paths so IDEs can open referenced files. For interactive monitoring, b2c logs tail streams entries until interrupted.

When to use it

• Investigating user reports like "throwing an error", "broken", or "not working" on server side.
• Fetching recent ERROR or FATAL entries after a failed controller call, job run, or custom API request.
• Searching for specific text such as exception class names, module names, or transaction IDs across recent logs.
• Filtering logs by time window to correlate errors with deployments or external events.
• Tailing logs in real time during manual reproduction or live debugging (human use).

Best practices

• Use --json for programmatic analysis and to get file names for full downloads via WebDAV.
• Combine --since, --level, and --search to quickly isolate relevant failures and reduce noise.
• Prefer recent relative times (e.g., 5m, 1h) when investigating live incidents; use ISO timestamps for historical lookups.
• List available log types with b2c logs list before querying to confirm which files exist.
• Use tail only for interactive troubleshooting; non-interactive agents should rely on logs get with --json.

Example use cases

• Run b2c logs get --since 1h --level ERROR --search "PaymentProcessor" --json to find recent payment failures.
• After a failing job, fetch job logs with b2c logs get --filter jobs --since 2h to inspect execution details.
• When a controller throws, search for controller class or pipeline names across error and customerror logs.
• List available logs with b2c logs list --json, then download a full file via the WebDAV skill using the returned file name.
• During a live demo or reproduction, use b2c logs tail --filter error --level ERROR to watch errors as they occur.