8000 [Feat]: Logs processing in Netdata · Issue #19464 · netdata/netdata · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
[Feat]: Logs processing in Netdata #19464
Open
@shyamvalsan

Description

@shyamvalsan

Problem

Netdata currently lacks native functionality for comprehensive log handling. This hinders the ability to easily collect, parse, visualize, and alert on log data within the Netdata ecosystem.

Description

Provide a unified approach for:

  • log ingestion: tail logs from disparate sources (files, k8s pods, journald, etc.)
  • log querying and visualization: enable real-time queries and display them within netdata dashboards
  • log processing: parse/extract key info from logs to create derived metrics and charts
  • log alerts: configure alerts on textual/log-based triggers (e.g., specific error strings)
  • log exporting: route logs to various backends (e.g., journald, s3, or other archival storage) based on user-defined policies

Importance

blocker

Value proposition

  1. improved observability by correlating logs with existing metrics
  2. easier troubleshooting workflow via netdata dashboard a single pane of glass
  3. reduces reliance on external tooling for basic log analytics
  4. streamlined data handling and potential cost savings by selective log routing
  5. enhances netdata's value as a comprehensive monitoring solution

Proposed implementation

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0