Units API.

See the Weblate's Web API documentation for detailed description of the API.

GET /api/units/873900/?format=api
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": [
        "Log files can also be managed by the `journald` daemon – a component of `systemd`. The `journald` daemon captures Syslog messages, kernel log messages, initial RAM disk and early boot messages as well as messages written to standard output and standard error output of all services, indexes them and makes this available to the user. The native journal file format, which is a structured and indexed binary file, improves searching and provides faster operation, and it also stores meta data information like time stamps or user IDs. Log files produced by `journald` are by default not persistent, log files are stored only in memory or a small ring-buffer in the `/run/log/journal/` directory. The amount of logged data depends on free memory, when you reach the capacity limit, the oldest entries are deleted. However, this setting can be altered – see xref:Viewing_and_Managing_Log_Files.adoc#s2-Enabling_Persistent_Storage[Enabling Persistent Storage]. For more information on Journal see xref:Viewing_and_Managing_Log_Files.adoc#s1-Using_the_Journal[Using the Journal]."
    ],
    "previous_source": "",
    "target": [
        "Log files can also be managed by the `journald` daemon – a component of `systemd`. The `journald` daemon captures Syslog messages, kernel log messages, initial RAM disk and early boot messages as well as messages written to standard output and standard error output of all services, indexes them and makes this available to the user. The native journal file format, which is a structured and indexed binary file, improves searching and provides faster operation, and it also stores meta data information like time stamps or user IDs. Log files produced by `journald` are by default not persistent, log files are stored only in memory or a small ring-buffer in the `/run/log/journal/` directory. The amount of logged data depends on free memory, when you reach the capacity limit, the oldest entries are deleted. However, this setting can be altered – see xref:Viewing_and_Managing_Log_Files.adoc#s2-Enabling_Persistent_Storage[Enabling Persistent Storage]. For more information on Journal see xref:Viewing_and_Managing_Log_Files.adoc#s1-Using_the_Journal[Using the Journal]."
    ],
    "id_hash": 7838134494222560623,
    "content_hash": 7838134494222560623,
    "location": "./pages/monitoring-and-automation/Viewing_and_Managing_Log_Files.adoc:14",
    "context": "",
    "note": "type: Plain text",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 4,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 152,
    "source_unit": "https://translate.fedoraproject.org/api/units/873900/?format=api",
    "priority": 100,
    "id": 873900,
    "web_url": "https://translate.fedoraproject.org/translate/fedora-docs-l10n-fedora-system-administrat/f29pagesmonitoring-and-automationviewing_and_managing_log_files/en/?checksum=ecc6a5cb55df2d6f",
    "url": "https://translate.fedoraproject.org/api/units/873900/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2020-02-24T22:18:03.129371Z"
}