Regenerate integrations.js (#18794)
Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>
Netdata bot committed
Oct 16, 2024 at 07:41 UTC
9a998b23e19ebf106906cdb0883729eb29381297
3 files changed
+93
integrations/integrations.js
+20
@@ -22331,6 +22331,26 @@ export const integrations = [
22331
"edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-notifications/metadata.yaml",
22332
"troubleshooting": ""
22333
},
22334
+ {
22335
+ "id": "logs-systemd-journal",
22336
+ "meta": {
22337
+ "name": "Systemd Journal Logs",
22338
+ "link": "https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md",
22339
+ "categories": [
22340
+ "logs"
22341
+ ],
22342
+ "icon_filename": "netdata.png"
22343
+ },
22344
+ "keywords": [
22345
+ "systemd",
22346
+ "journal",
22347
+ "logs"
22348
+ ],
22349
+ "overview": "# Systemd Journal Logs\n\nThe `systemd` journal plugin by Netdata makes viewing, exploring and analyzing `systemd` journal logs simple and efficient.\n\nIt 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.\n\nThe 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).\n\n\n## Visualization\n\nYou can start exploring `systemd` journal logs on the \"Logs\" tab of the Netdata UI.\n\n\n## Key features\n\n- Works on both **individual servers** and **journal centralization servers**.\n- Supports `persistent` and `volatile` journals.\n- Supports `system`, `user`, `namespaces` and `remote` journals.\n- Allows filtering on **any journal field** or **field value**, for any time-frame.\n- Allows **full text search** (`grep`) on all journal fields, for any time-frame.\n- Provides a **histogram** for log entries over time, with a break down per field-value, for any field and any time-frame.\n- Works directly on journal files, without any other third-party components.\n- Supports coloring log entries, the same way `journalctl` does.\n- In PLAY mode provides the same experience as `journalctl -f`, showing new log entries immediately after they are received.\n",
22350
+ "setup": "## Setup\n\n## Prerequisites\n\n- A Netdata Cloud account\n\n\n## Configuration\n\nThere is no configuration needed for this integration.\n",
22351
+ "integration_type": "logs",
22352
+ "edit_link": "https://github.com/netdata/netdata/blob/master/integrations/logs/metadata.yaml"
22353
+ },
22354
{
22355
"id": "oidc-authentication",
22356
"meta": {
integrations/integrations.json
+20
@@ -22329,6 +22329,26 @@
22329
"edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-notifications/metadata.yaml",
22330
"troubleshooting": ""
22331
},
22332
+ {
22333
+ "id": "logs-systemd-journal",
22334
+ "meta": {
22335
+ "name": "Systemd Journal Logs",
22336
+ "link": "https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md",
22337
+ "categories": [
22338
+ "logs"
22339
+ ],
22340
+ "icon_filename": "netdata.png"
22341
+ },
22342
+ "keywords": [
22343
+ "systemd",
22344
+ "journal",
22345
+ "logs"
22346
+ ],
22347
+ "overview": "# Systemd Journal Logs\n\nThe `systemd` journal plugin by Netdata makes viewing, exploring and analyzing `systemd` journal logs simple and efficient.\n\nIt 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.\n\nThe 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).\n\n\n## Visualization\n\nYou can start exploring `systemd` journal logs on the \"Logs\" tab of the Netdata UI.\n\n\n## Key features\n\n- Works on both **individual servers** and **journal centralization servers**.\n- Supports `persistent` and `volatile` journals.\n- Supports `system`, `user`, `namespaces` and `remote` journals.\n- Allows filtering on **any journal field** or **field value**, for any time-frame.\n- Allows **full text search** (`grep`) on all journal fields, for any time-frame.\n- Provides a **histogram** for log entries over time, with a break down per field-value, for any field and any time-frame.\n- Works directly on journal files, without any other third-party components.\n- Supports coloring log entries, the same way `journalctl` does.\n- In PLAY mode provides the same experience as `journalctl -f`, showing new log entries immediately after they are received.\n",
22348
+ "setup": "## Setup\n\n## Prerequisites\n\n- A Netdata Cloud account\n\n\n## Configuration\n\nThere is no configuration needed for this integration.\n",
22349
+ "integration_type": "logs",
22350
+ "edit_link": "https://github.com/netdata/netdata/blob/master/integrations/logs/metadata.yaml"
22351
+ },
22352
{
22353
"id": "oidc-authentication",
22354
"meta": {
integrations/logs/integrations/systemd_journal_logs.md
new
+53
@@ -0,0 +1,53 @@
1
+<!--startmeta
2
+custom_edit_url: "https://github.com/netdata/netdata/edit/master/integrations/logs/README.md"
3
+meta_yaml: "https://github.com/netdata/netdata/edit/master/integrations/logs/metadata.yaml"
4
+sidebar_label: "Systemd Journal Logs"
5
+learn_status: "Published"
6
+learn_rel_path: "Logs"
7
+message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE LOGS' metadata.yaml FILE"
8
+endmeta-->
9
+
10
+# Systemd Journal Logs
11
+
12
+
13
+<img src="https://netdata.cloud/img/netdata.png" width="150"/>
14
+
15
+
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
+
22
+
23
+<img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" />
24
+
25
+## Visualization
26
+
27
+You can start exploring `systemd` journal logs on the "Logs" tab of the Netdata UI.
28
+
29
+
30
+## Key features
31
+
32
+- Works on both **individual servers** and **journal centralization servers**.
33
+- Supports `persistent` and `volatile` journals.
34
+- Supports `system`, `user`, `namespaces` and `remote` journals.
35
+- Allows filtering on **any journal field** or **field value**, for any time-frame.
36
+- Allows **full text search** (`grep`) on all journal fields, for any time-frame.
37
+- Provides a **histogram** for log entries over time, with a break down per field-value, for any field and any time-frame.
38
+- Works directly on journal files, without any other third-party components.
39
+- Supports coloring log entries, the same way `journalctl` does.
40
+- In PLAY mode provides the same experience as `journalctl -f`, showing new log entries immediately after they are received.
41
+
42
+
43
+## Setup
44
+
45
+## Prerequisites
46
+
47
+- A Netdata Cloud account
48
+
49
+
50
+## Configuration
51
+
52
+There is no configuration needed for this integration.
53
+