GiteraGitera Docs

Log search

Instant substring search across every indexed CI/CD log line in the organization — with facet filters and saved presets.

Open in Gitera

/logs searches raw job log lines across all repositories without opening a single GitHub run page.

Query syntax

Search is substring-based and case-insensitive:

InputMatches lines containing
ETIMEDOUTthe substring ETIMEDOUT
docker pushboth substrings docker and push (terms are AND-ed)
"Connection reset by peer"the exact substring Connection reset by peer
  • Minimum query length: 3 characters.
  • * and ? are literal characters, not wildcards — there is no regex or boolean (AND/OR) syntax.
  • Add terms to narrow; the more specific the phrase, the fewer hits.

Filters

Refine results with checkboxes for repository, workflow file, and run conclusion (success, failure, cancelled, …). Filters combine with the search text and the global time range.

Results

  • Hits are listed per step with repository, workflow, run, and timestamps, and matching terms are highlighted inside each line.
  • Open a hit to see the full step context around the line.
  • Results paginate — load more with the button at the bottom of the list.

Saved presets

Save a frequent query together with its filters and time range (for example OOM killed, Docker push failed). Presets are stored per user and loadable in one click — handy for on-call routines.

Only logs inside your plan's retention window are searchable, and only for runs that started after you connected (logs are not backfilled). See Plans and limits and Missing logs.

On this page