fetch-deployment-logs

To fetch deployment logs for production debugging, call fetchDeploymentLogs to retrieve recent entries and begin analysis. The skill isolates errors and warnings by filtering on message content and surrounding context to diagnose outages.

Yes, you can filter production logs using afterTimestamp and beforeTimestamp parameters to specify time ranges. You can also apply message and messageContext parameters to isolate specific errors, warnings, or traces during deployment monitoring.

The best way to analyze deployment logs for runtime errors is to filter by message patterns to isolate failures, then retrieve surrounding context for matched entries. This contextualizes adjacent events to identify root causes during outages.

You get surrounding context for matched log entries by applying the messageContext parameter when fetching deployment logs. This retrieves adjacent events around matched patterns, helping you understand the sequence of failures leading to an outage.

Yes, fetching deployment logs for monitoring and troubleshooting works across different environments. The skill is applicable for debugging outages, monitoring ongoing runtime behavior, and verifying performance across multiple deployment targets.

Filtering deployment logs by timestamp using afterTimestamp and beforeTimestamp narrows the output to specific deployment windows. This prevents information overload and accelerates diagnosing issues tied to recent production changes.