File: api-logs-html.adoc

package info (click to toggle)
cockpit 358-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 317,272 kB
  • sloc: javascript: 775,788; python: 41,626; ansic: 33,970; cpp: 11,141; sh: 3,566; makefile: 581; xml: 262
file content (67 lines) | stat: -rw-r--r-- 2,312 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
= logs.html

System log component

[[api-logs-html-description]]
== Description
....
<iframe src="http://127.0.0.1:9090/cockpit+app/@localhost/system/logs.html"
    width="600" height="400"></iframe>
....

This is a Cockpit component that brings up system log viewer, with
filtering capabilities. On systemd based systems this displays the
entries from journal.

Component URL::
  `+/cockpit+app/@localhost/system/logs.html+`
Filter by priority::
  `+#?prio=notice+` +
   +
  Filters the log to show entries below the specific priority,
  inclusive. These
  https://en.wikipedia.org/wiki/Syslog#Severity_levels[priorities are
  syslog level keywords]. Specifying `+*+` as a priority will show all
  available entries. The default priority is `+err+`.
Filter by service::
  `+#?service=sshd.service+` +
   +
  Filters the log to show entries related to the specific service. The
  format of the service is specific to the logging implementation. For
  journald these are systemd service unit names.
Filter by tag::
  `+#?tag=kernel+` +
   +
  Filters the log to show entries related to the specific syslog
  identifier.
Filter by message::
  `+#?grep=+` +
   +
  Filters the log to show entries where the `+MESSAGE=+` field matches
  the specified regular expression. PERL-compatible regular expressions
  are used. If the pattern is all lowercase, matching is case
  insensitive. Otherwise, matching is case sensitive.
Filter by any field::
  `+#?FIELD=VALUE+` +
   +
  A field is referring to the components of a structured journal entry.
  The match must be exact. Value can be comma separated list in which
  case they are automatically matched as alternatives.
Start at point::
  `+#?start=boot+` +
   +
  Filters the log to show entries after the specific point in time.
  Valid values are `+boot+` (since last boot), `+last-24h+` (last 24
  hours), `+last-week+` (last seven days) and `+previous-boot+`
  (previous boot).
Follow the journal::
  `+#?follow=true+` +
   +
  Keep listening on new entries. Valid values are `+true+` (follow) and
  `+false+` (do not follow).
Show log entry::
  `+#/6e272d82993c4e0d...+` +
   +
  To show a specific log entry, put the log entry cursor in a path after
  the hash above. Note that cursors are logging system specific, and
  journal cursors are subject to change.