| 1 | # yamllint disable rule:line-length |
| 2 | --- |
| 3 | - id: "logs-systemd-journal" |
| 4 | meta: |
| 5 | name: "Systemd Journal Logs" |
| 6 | link: "https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md" |
| 7 | categories: |
| 8 | - logs |
| 9 | icon_filename: "netdata.png" |
| 10 | keywords: |
| 11 | - systemd |
| 12 | - journal |
| 13 | - logs |
| 14 | overview: |
| 15 | description: | |
| 16 | The `systemd` journal plugin by Netdata makes viewing, exploring and analyzing `systemd` journal logs simple and efficient. |
| 17 | |
| 18 | It automatically discovers available journal sources, allows advanced filtering, offers interactive visual representations and supports exploring the logs of both individual servers and the logs on infrastructure wide journal centralization servers. |
| 19 | |
| 20 | The plugin automatically detects the available journal sources, based on the journal files available in `/var/log/journal` (persistent logs) and `/run/log/journal` (volatile logs). |
| 21 | visualization: |
| 22 | description: | |
| 23 | You can start exploring `systemd` journal logs on the "Logs" tab of the Netdata UI. |
| 24 | key_features: |
| 25 | description: | |
| 26 | - Works on both **individual servers** and **journal centralization servers**. |
| 27 | - Supports `persistent` and `volatile` journals. |
| 28 | - Supports `system`, `user`, `namespaces` and `remote` journals. |
| 29 | - Allows filtering on **any journal field** or **field value**, for any time-frame. |
| 30 | - Allows **full text search** (`grep`) on all journal fields, for any time-frame. |
| 31 | - Provides a **histogram** for log entries over time, with a break down per field-value, for any field and any time-frame. |
| 32 | - Works directly on journal files, without any other third-party components. |
| 33 | - Supports coloring log entries, the same way `journalctl` does. |
| 34 | - In PLAY mode provides the same experience as `journalctl -f`, showing new log entries immediately after they are received. |
| 35 | setup: |
| 36 | prerequisites: |
| 37 | description: | |
| 38 | - A Netdata Cloud account |
| 39 | - id: "windows-event-logs" |
| 40 | meta: |
| 41 | name: "Windows Event Logs" |
| 42 | link: "https://github.com/netdata/netdata/blob/master/src/collectors/windows-events.plugin/README.md" |
| 43 | categories: |
| 44 | - logs |
| 45 | icon_filename: "windows.svg" |
| 46 | keywords: |
| 47 | - windows |
| 48 | - windows events |
| 49 | - logs |
| 50 | overview: |
| 51 | description: | |
| 52 | The Windows Events plugin by Netdata makes viewing, exploring and analyzing Windows Events simple and |
| 53 | efficient. |
| 54 | |
| 55 | The plugin automatically detects all the available channels and offers a list of "Event Channels". |
| 56 | |
| 57 | By default, it aggregates events from all event channels, providing a unified view of all events. |
| 58 | visualization: |
| 59 | description: | |
| 60 | You can start exploring Windows event logs on the "Logs" tab of the Netdata UI. |
| 61 | key_features: |
| 62 | description: | |
| 63 | - Supports **Windows Event Logs (WEL)**. |
| 64 | - Supports **Event Tracing for Windows (ETW)** and **TraceLogging (TL)**, when events are routed to Event Log. |
| 65 | - Allows filtering on all System Events fields. |
| 66 | - Allows **full text search** (`grep`) on all System and User fields. |
| 67 | - Provides a **histogram** for log entries over time, with a break down per field-value, for any System Event field and any |
| 68 | time-frame. |
| 69 | - Supports coloring log entries based on severity. |
| 70 | - In PLAY mode it "tails" all the Events, showing new log entries immediately after they are received. |
| 71 | setup: |
| 72 | prerequisites: |
| 73 | description: | |
| 74 | - Netdata Cloud paid subscription |
| 75 | - id: "logs-opentelemetry" |
| 76 | meta: |
| 77 | name: "OpenTelemetry Logs" |
| 78 | link: "https://github.com/netdata/netdata/blob/master/src/crates/netdata-log-viewer/README.md" |
| 79 | categories: |
| 80 | - logs |
| 81 | icon_filename: "opentelemetry.svg" |
| 82 | keywords: |
| 83 | - opentelemetry |
| 84 | - otel |
| 85 | - otlp |
| 86 | - logs |
| 87 | overview: |
| 88 | description: | |
| 89 | The OpenTelemetry log viewer plugin by Netdata makes viewing, exploring and analyzing OpenTelemetry logs simple and efficient. |
| 90 | |
| 91 | It works with logs ingested by the `otel.plugin`, which receives OTLP-formatted log data and stores them in |
| 92 | systemd-compatible journal files. The log viewer provides the same powerful exploration interface used for |
| 93 | systemd journal logs. |
| 94 | visualization: |
| 95 | description: | |
| 96 | You can start exploring OpenTelemetry logs on the "Logs" tab of the Netdata UI. |
| 97 | key_features: |
| 98 | description: | |
| 99 | - Views logs ingested via **OpenTelemetry OTLP/gRPC** protocol. |
| 100 | - Allows filtering on **any log field** or **field value**, for any time-frame. |
| 101 | - Allows **full text search** (`grep`) on all log fields, for any time-frame. |
| 102 | - Provides a **histogram** for log entries over time, with a break down per field-value, for any field and any time-frame. |
| 103 | - Uses **fast indexed lookups** with pre-built indexes for performance. |
| 104 | - Supports **faceted search** across log fields (severity, hostname, service, etc.). |
| 105 | - In PLAY mode shows new log entries immediately after they are received. |
| 106 | setup: |
| 107 | prerequisites: |
| 108 | description: | |
| 109 | - A Netdata Cloud account |
| 110 | - The `otel.plugin` configured to ingest OpenTelemetry logs |