X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-journal-gatewayd.service.xml;fp=man%2Fsystemd-journal-gatewayd.service.xml;h=9b0fce60979b1c68ba55084fc83f1fe0bdfa7504;hb=ee7c77db55cb105e69f1a088539da602c706c611;hp=0000000000000000000000000000000000000000;hpb=4a1909bb6655a1ba84b426546acb9a518aa9b679;p=elogind.git diff --git a/man/systemd-journal-gatewayd.service.xml b/man/systemd-journal-gatewayd.service.xml new file mode 100644 index 000000000..9b0fce609 --- /dev/null +++ b/man/systemd-journal-gatewayd.service.xml @@ -0,0 +1,249 @@ + + + + + + + + + systemd-journal-gatewayd.service + systemd + + + + Developer + Zbigniew + Jędrzejewski-Szmek + zbyszek@in.waw.pl + + + + + + systemd-journal-gatewayd.service + 8 + + + + systemd-journal-gatewayd.service + systemd-journal-gatewayd.socket + systemd-journal-gatewayd + HTTP server for journal events + + + + systemd-journal-gatewayd.service + systemd-journal-gatewayd.socket + /usr/lib/systemd/systemd-journal-gatewayd + + + + + Description + + systemd-journal-gatewayd serves journal + events over the network. Clients must connect using + HTTP, to port 19531 by default. + + 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. + + + + Supported URLs + + The following URLs are recognized: + + + + + + Interactive browsing. + + + + + + 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. + + + + + + + Accept header + + + + + + Recognized formats: + + + + + + The default. Plaintext syslog-like output, + one line per journal entry + (like journalctl --output short). + + + + + + + Entries are formatted as JSON data structures, + one per line + (like journalctl --output json). + See Journal + JSON Format for more information. + + + + + + + Entries are formatted as JSON data structures, + wrapped in a format suitable for + Server-Sent Events + (like journalctl --output json-sse). + + + + + + + + Entries 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 header + + + + + + where + is a cursor string, + is an integer, + is an unsigned integer. + + + Range defaults to all available events. + + + + URL GET parameters + + Following parameters can be used as part of the URL: + + + + + + wait for new events + (like journalctl --follow, except that + the number of events returned is not limited). + + + + + + + Test that the specified cursor refers to an + entry in the journal. Returns just this entry. + + + + + + + Limit events to the current boot of the system + (like journalctl --this--boot). + + + + + + Match journal fields. See + systemd.journal-fields7. + + + + + + + Examples + Retrieve 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 Also + + systemd1, + journalctl1, + systemd-journald.service8, + systemd.journal-fields7, + + + +