fetch-deployment-logs

To fetch deployment logs for production debugging, retrieve entries within specific time windows and apply RE2 regex message matching to filter runtime errors. This isolates incident-time behavior and returns formatted logs with a found or empty indicator.

Investigating server startup crashes requires fetching deployment logs from the incident window. You can apply regex filtering with configurable context lines to expose surrounding stack traces and pinpoint the root cause of the runtime failure.

You can filter production logs using optional RE2 regex message matching. The retrieval supports configurable context lines and match limits, returning formatted log entries that expose stack traces and root causes for broken pages or missing functionality.

For incident response runtime error investigation, fetch deployment logs filtered by after or before timestamps. This targeted log retrieval confirms what errors occurred during recent deployments and returns matching entries with a found or empty status indicator.

Troubleshooting a broken page after publishing requires fetching deployment logs within optional time windows. Specifying after and before timestamps isolates the exact deployment period, returning formatted matching log lines to diagnose the production failure.

Serverless error investigation applies configurable match limits to regex-filtered deployment logs. This constrains the returned formatted log entries and context lines, ensuring focused debugging without exceeding retrieval bounds during production failure analysis.