Logging
Fastest way to search and filter logs across all CI jobs running on Blacksmith runners
Whether you’re triaging a broken build in a pull request or digging into a flaky test that only happens on main, logs are now a much better experience in GitHub Actions. You’ll be able to zoom in locally or investigate patterns globally across all your CI runs.
Query Syntax Guide
Let’s break down the query syntax:
Property Filters
You can search and filter your logs using the following criteria:
Filter | Description |
---|---|
run_id:* | Filter by workflow run instances (each run may contain multiple jobs) |
run_attempt:* | Filter by the attempt number of a given workflow run |
workflow:* | Filter by GitHub workflow name |
pr:* | Filter by pull request number |
branch:* | Filter by Git branch associated with the run |
repo:* | Filter by repository name |
job_id:* | Filter by specific job IDs |
job_name:* | Filter by job names |
step_id:* | Filter by specific step IDs |
step_name:* | Filter by workflow step names |
user:* | Filter by the user who triggered the workflow |
level:* | Filter by severity (info , warn , debug , error ) |
In this example, we are filtering for logs from the main
branch and only showing logs with severity error
or warn
:
Substring Search
You can search for text across your logs using the log search bar. For multi-word phrases, use quotes. In this example, we are searching for logs containing the phrase “failed”:
Exclude Matches
You can exclude matches by prefixing a search term with -
. In this example, we are excluding logs containing the phrase “econn refused”: