Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://translate.fedoraproject.org/api/translations/fedora-docs-l10n-fedora-system-administrat/f29pagesmonitoring-and-automationviewing_and_managing_log_files/en/?format=api",
    "source": [
        "By default, only `journald` is installed on your system. You have to install rsyslog youself. Also do not forget to enable and start it after install before continuing with rest of this guide.  The `journald` daemon is the primary tool for troubleshooting. It also provides additional data necessary for creating structured log messages. Data acquired by `journald` is forwarded into the `/run/systemd/journal/syslog` socket that may be used by `rsyslogd` to process the data further. However, [application]*rsyslog* does the actual integration by default via the `imjournal` input module, thus avoiding the aforementioned socket. You can also transfer data in the opposite direction, from `rsyslogd` to `journald` with use of `omjournal` module. See xref:Viewing_and_Managing_Log_Files.adoc#s1-interaction_of_rsyslog_and_journal[Interaction of Rsyslog and Journal] for further information. The integration enables maintaining text-based logs in a consistent format to ensure compatibility with possible applications or configurations dependent on `rsyslogd`. Also, you can maintain rsyslog messages in a structured format (see xref:Viewing_and_Managing_Log_Files.adoc#s1-structured_logging_with_rsyslog[Structured Logging with Rsyslog])."
    ],
    "previous_source": "",
    "target": [
        "By default, only `journald` is installed on your system. You have to install rsyslog youself. Also do not forget to enable and start it after install before continuing with rest of this guide.  The `journald` daemon is the primary tool for troubleshooting. It also provides additional data necessary for creating structured log messages. Data acquired by `journald` is forwarded into the `/run/systemd/journal/syslog` socket that may be used by `rsyslogd` to process the data further. However, [application]*rsyslog* does the actual integration by default via the `imjournal` input module, thus avoiding the aforementioned socket. You can also transfer data in the opposite direction, from `rsyslogd` to `journald` with use of `omjournal` module. See xref:Viewing_and_Managing_Log_Files.adoc#s1-interaction_of_rsyslog_and_journal[Interaction of Rsyslog and Journal] for further information. The integration enables maintaining text-based logs in a consistent format to ensure compatibility with possible applications or configurations dependent on `rsyslogd`. Also, you can maintain rsyslog messages in a structured format (see xref:Viewing_and_Managing_Log_Files.adoc#s1-structured_logging_with_rsyslog[Structured Logging with Rsyslog])."
    ],
    "id_hash": -5680163565803879058,
    "content_hash": -5680163565803879058,
    "location": "./pages/monitoring-and-automation/Viewing_and_Managing_Log_Files.adoc:16",
    "context": "",
    "note": "type: Plain text",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 5,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 155,
    "source_unit": "https://translate.fedoraproject.org/api/units/873906/?format=api",
    "priority": 100,
    "id": 873906,
    "web_url": "https://translate.fedoraproject.org/translate/fedora-docs-l10n-fedora-system-administrat/f29pagesmonitoring-and-automationviewing_and_managing_log_files/en/?checksum=312c0154ea24c56e",
    "url": "https://translate.fedoraproject.org/api/units/873906/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2020-02-24T22:18:03.161133Z"
}