Logs
Logs give you the raw operational trail behind an alert or a player report. Search is available network-wide and per server.
Before you start
Section titled “Before you start”Log ingestion is disabled by default on the connector because logs can contain sensitive text.
Opening logs
Section titled “Opening logs”- Network logs:
/logssearches across the servers in your organization. - Server logs: a server’s Logs page restricts search to that server.
Query language
Section titled “Query language”| Query | Effect |
|---|---|
level:error,warn | Filter by one or more levels: trace, debug, info, warn, error, fatal. |
logger:"com.example.Plugin" | Filter by logger name. |
stacktrace:true | Only entries with a stack trace. |
| free text | Substring search over the message. |
The query bar offers autocomplete, recent searches, and syntax highlighting. Filters are also available as controls: time range, levels, logger, and stack-trace presence. All filter state lives in the URL, so a search can be shared.
Search is substring-based. Regular expressions are not supported.
Histogram and results
Section titled “Histogram and results”- A stacked histogram shows log volume by level over the selected window; click a bar to narrow the time range.
- Results stream in a virtualised table for large volumes, with pagination or infinite scroll.
- The default window is the last 6 hours and the default page size is 100, up to a maximum of 500 entries per request.
Entry detail
Section titled “Entry detail”Open an entry to see the full message, logger, thread, trace and span IDs, custom attributes, and a collapsible stack trace. Copying preserves the full entry for pasting into an issue.
Current limits
Section titled “Current limits”- Substring search only, no regex or full-text ranking.
- Polling rather than a live tail.
- Retention follows platform policy; exports are not available from the log view.