metadata.yaml 3.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475
  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. 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.
  18. 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).
  19. visualization:
  20. description: |
  21. You can start exploring `systemd` journal logs on the "Logs" tab of the Netdata UI.
  22. key_features:
  23. description: |
  24. - Works on both **individual servers** and **journal centralization servers**.
  25. - Supports `persistent` and `volatile` journals.
  26. - Supports `system`, `user`, `namespaces` and `remote` journals.
  27. - Allows filtering on **any journal field** or **field value**, for any time-frame.
  28. - Allows **full text search** (`grep`) on all journal fields, for any time-frame.
  29. - Provides a **histogram** for log entries over time, with a break down per field-value, for any field and any time-frame.
  30. - Works directly on journal files, without any other third-party components.
  31. - Supports coloring log entries, the same way `journalctl` does.
  32. - In PLAY mode provides the same experience as `journalctl -f`, showing new log entries immediately after they are received.
  33. setup:
  34. prerequisites:
  35. description: |
  36. - A Netdata Cloud account
  37. - id: "windows-event-logs"
  38. meta:
  39. name: "Windows Event Logs"
  40. link: "https://github.com/netdata/netdata/blob/master/src/collectors/windows-events.plugin/README.md"
  41. categories:
  42. - logs
  43. - data-collection.windows-systems
  44. icon_filename: "windows.svg"
  45. keywords:
  46. - windows
  47. - windows events
  48. - logs
  49. overview:
  50. description: |
  51. The Windows Events plugin by Netdata makes viewing, exploring and analyzing Windows Events simple and
  52. efficient.
  53. The plugin automatically detects all the available channels and offers a list of "Event Channels".
  54. By default, it aggregates events from all event channels, providing a unified view of all events.
  55. visualization:
  56. description: |
  57. You can start exploring Windows event logs on the "Logs" tab of the Netdata UI.
  58. key_features:
  59. description: |
  60. - Supports **Windows Event Logs (WEL)**.
  61. - Supports **Event Tracing for Windows (ETW)** and **TraceLogging (TL)**, when events are routed to Event Log.
  62. - Allows filtering on all System Events fields.
  63. - Allows **full text search** (`grep`) on all System and User fields.
  64. - Provides a **histogram** for log entries over time, with a break down per field-value, for any System Event field and any
  65. time-frame.
  66. - Supports coloring log entries based on severity.
  67. - In PLAY mode it "tails" all the Events, showing new log entries immediately after they are received.
  68. setup:
  69. prerequisites:
  70. description: |
  71. - Netdata Cloud paid subscription