0
0
Fork 0
mirror of https://github.com/netdata/netdata.git synced 2025-04-06 14:35:32 +00:00

Update README.md

This commit is contained in:
Costa Tsaousis 2024-03-17 23:07:51 +02:00 committed by GitHub
parent 283cd665c3
commit f05f47bcbd
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -1,5 +1,52 @@
# Logs Centralization Points with systemd-journald
```mermaid
stateDiagram-v2
classDef userFeature fill:#f00,color:white,font-weight:bold,stroke-width:2px,stroke:yellow
classDef usedByNC fill:#090,color:white,font-weight:bold,stroke-width:2px,stroke:yellow
classDef thirdparty fill:#333,color:#aaa,font-weight:normal,stroke-width:1px,stroke:#fff
logsQuery:::usedByNC
logsDashboard:::userFeature
journald:::thirdparty
journalRemote:::thirdparty
journalUpload:::thirdparty
journalFiles:::thirdparty
logSources:::thirdparty
textFiles:::thirdparty
journalRemote: systemd-journal-remote
journalUpload: systemd-journal-upload
journalFiles: Store
journalFiles: systemd-journal files
journald: systemd-journald
logSources: Local Logs Sources
log2journal:log2journal
log2journal:Convert text, json, logfmt files
log2journal:to structured journal entries.
logsDashboard: Netdata Dashboards
logsQuery: Query Journal Files
textFiles: Text Log Files
logSources --> journald: journald API
logSources --> textFiles: write to log files
textFiles --> log2journal: tail log files
log2journal --> journald: journald API
journald --> journalFiles
journalFiles --> Netdata
journalFiles --> journalUpload
journalRemote -->journalFiles
journalUpload --> [*]: to a remote journald
[*] --> journalRemote: from a remote journald
state Netdata {
[*]-->logsQuery
logsQuery --> logsDashboard
}
```
Logs centralization points can be built using the `systemd-journald` methodologies, by configuring `systemd-journal-remote` (on the centralization point) and `systemd-journal-upload` (on the production system).
The logs centralization points and the metrics centralization points do not need to be the same. For clarity and simplicity however, when not otherwise required for operational or regulatory reasons, we recommend to have unified centralization points for both metrics and logs.