Go Links
Go links let you construct URLs that open Oodle pages with pre-configured filters, time ranges, columns, and sort order. Use them to link directly from runbooks, alerts, CI pipelines, or chat messages into a specific view of your observability data.
Available Go Links
| Go Link | Destination |
|---|---|
/go/logs | Logs Explorer |
Logs Go Link
https://<your-instance>.oodle.ai/go/logs?<params>
Redirects to the Logs Explorer with the specified filters, time range, columns, and sort order pre-applied.
Parameters
| Parameter | Description | Default |
|---|---|---|
start | Start time in ISO 8601 format (e.g. 2026-01-15T08:00:00Z) | Now minus 15 minutes |
end | End time in ISO 8601 format | Now |
query | Lucene query string | None |
_columns | Comma-separated list of columns to display | timestamp,message |
_sort | Column name to sort by | timestamp |
_sort_order | Sort direction: asc or desc | desc |
| Any other param | Becomes a field filter (see Filters) | — |
Time Range
When neither start nor end is provided, the
explorer opens with a relative last-15-minute
window. If either is provided, the time range becomes
absolute:
- Only
start— end defaults to now - Only
end— start defaults to 15 minutes before end - Both — exact window
/go/logs?start=2026-01-15T08:00:00Z&end=2026-01-15T09:00:00Z
Filters
Any query parameter that is not a reserved name (see the table above) is treated as a field filter. The parameter name is the field, and the value is matched with an "is one of" filter.
Multiple values for the same field are supported in two ways:
Comma-separated values:
/go/logs?level=ERROR,WARN
Repeated parameters:
/go/logs?level=ERROR&level=WARN
Both produce the same filter:
level is one of [ERROR, WARN].
You can combine multiple fields — each becomes a separate filter:
/go/logs?level=ERROR&container_name=api-server
Columns
Use _columns to control which columns appear in the
results table. The timestamp column is always included
as the first column, even if omitted.
/go/logs?_columns=timestamp,level,message,container_name
Sort Order
Use _sort and _sort_order to control how results
are sorted. When omitted, logs are sorted by
timestamp descending (newest first).
/go/logs?_sort=level&_sort_order=asc
If only _sort_order is provided, the sort column
defaults to timestamp:
/go/logs?_sort_order=asc
Query
Use query to pass a Lucene query string that appears
in the search bar:
/go/logs?query=message:timeout AND level:ERROR
Examples
Show errors from the last 15 minutes:
/go/logs?level=ERROR
Show warnings and errors with custom columns:
/go/logs?level=ERROR,WARN&_columns=timestamp,level,message,container_name
Search a specific time window with a Lucene query:
/go/logs?start=2026-01-15T08:00:00Z&end=2026-01-15T09:00:00Z&query=status:503
Filter by multiple fields, sort oldest first:
/go/logs?level=ERROR&container_name=payment-service&_sort_order=asc
Best Practices
- Prefer relative time ranges — omit
startandendso the link always shows recent data. Use absolute times only when linking to a known incident window. - Keep links readable — use comma-separated values
(
level=ERROR,WARN) instead of repeated parameters when practical. - Include
_columnswhen linking from runbooks so responders see the most relevant fields immediately. - URL-encode special characters — values containing spaces, commas within a single value, or other special characters should be percent-encoded.
Support
If you have any questions or need assistance, contact us via the help chat or email support@oodle.ai.