systemd-journal-gatewayd.servicesystemdsystemd-journal-gatewayd.service8systemd-journal-gatewayd.servicesystemd-journal-gatewayd.socketsystemd-journal-gatewaydHTTP server for journal eventssystemd-journal-gatewayd.servicesystemd-journal-gatewayd.socket/usr/lib/systemd/systemd-journal-gatewaydOPTIONSDescriptionsystemd-journal-gatewayd serves journal
events over the network. Clients must connect using
HTTP. The server listens on port 19531 by default.
If is specified, the server expects
HTTPS connections.The program is started by
systemd1
and expects to receive a single socket. Use
systemctl start systemd-journal-gatewayd.socket to start
the service, and systemctl enable systemd-journal-gatewayd.socket
to have it started on boot.OptionsThe following options are understood:Specify the path to a file or AF_UNIX stream socket to read the
server certificate from. The certificate must be in PEM format. This option switches
systemd-journal-gatewayd into HTTPS mode and must be used together with
.Specify the path to a file or AF_UNIX stream socket to read the
secret server key corresponding to the certificate specified with from. The
key must be in PEM format.Specify the path to a file or AF_UNIX stream socket to read a CA
certificate from. The certificate must be in PEM format.Takes a directory path as argument. If
specified, systemd-journal-gatewayd will serve the
specified journal directory DIR instead of
the default runtime and system journal paths.Supported URLsThe following URLs are recognized:/browseInteractive browsing./entries[?option1&option2=value…]Retrieval of events in various formats.The part of the HTTP header
determines the format. Supported values are described below.
The part of the HTTP header
determines the range of events returned. Supported values are
described below.
GET parameters can be used to modify what events are
returned. Supported parameters are described below./machineReturn a JSON structure describing the machine.Example:
{ "machine_id" : "8cf7ed9d451ea194b77a9f118f3dc446",
"boot_id" : "3d3c9efaf556496a9b04259ee35df7f7",
"hostname" : "fedora",
"os_pretty_name" : "Fedora 19 (Rawhide)",
"virtualization" : "kvm",
…}/fields/FIELD_NAMEReturn a list of values of this field present in the logs.Accept headerRecognized formats:text/plainThe default. Plaintext syslog-like output,
one line per journal entry
(like journalctl --output short).application/jsonEntries are formatted as JSON data structures,
one per line
(like journalctl --output json).
See Journal
JSON Format for more information.text/event-streamEntries are formatted as JSON data structures,
wrapped in a format suitable for
Server-Sent Events
(like journalctl --output json-sse).
application/vnd.fdo.journalEntries are serialized into a binary (but
mostly text-based) stream suitable for backups and network
transfer
(like journalctl --output export).
See Journal
Export Format for more information.Range headerwhere
cursor is a cursor string,
num_skip is an integer,
num_entries is an unsigned integer.
Range defaults to all available events.URL GET parametersFollowing parameters can be used as part of the URL:followwait for new events
(like journalctl --follow, except that
the number of events returned is not limited).discreteTest that the specified cursor refers to an
entry in the journal. Returns just this entry.bootLimit events to the current boot of the system
(like journalctl -b).KEY=matchMatch journal fields. See
systemd.journal-fields7.ExamplesRetrieve events from this boot from local journal
in Journal
Export Format:
curl --silent -H'Accept: application/vnd.fdo.journal' \
'http://localhost:19531/entries?boot'Listen for core dumps:
curl 'http://localhost:19531/entries?follow&MESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1'See Alsosystemd1,
journalctl1,
systemd.journal-fields7,
systemd-journald.service8,
systemd-journal-remote.service8,
systemd-journal-upload.service8