mon
/
pb-dydns
1
0
Fork 0
Code Issues 8 Pull Requests Packages Projects Releases Wiki Activity

Evaluate adding structured logging alongside human‑readable logs #6

New Issue
Open
opened 2026-04-07 11:01:11 +01:00 by mon · 0 comments
mon commented 2026-04-07 11:01:11 +01:00
Owner
Copy Link

Currently, logs are plain text optimized for human readability. This issue proposes evaluating whether to add optional structured logging (e.g., JSON lines) to support automated log processing, monitoring, or integration with external tools.

Discussion points

  • Should structured logs be optional (e.g., via config flag)?
  • Should logs remain human‑readable by default?
  • What fields would be useful in structured form (timestamp, event type, domain, record, old/new IP, status)?
  • Would dual‑format logging (human + JSON) be beneficial?

Benefits

  • Easier integration with log parsers, dashboards, or alerting systems
  • Machine‑readable logs for long‑term analysis
  • More consistent structure for automated tools

Decision should consider simplicity vs. flexibility

Currently, logs are plain text optimized for human readability. This issue proposes evaluating whether to add optional structured logging (e.g., JSON lines) to support automated log processing, monitoring, or integration with external tools. **Discussion points** - Should structured logs be optional (e.g., via config flag)? - Should logs remain human‑readable by default? - What fields would be useful in structured form (timestamp, event type, domain, record, old/new IP, status)? - Would dual‑format logging (human + JSON) be beneficial? **Benefits** - Easier integration with log parsers, dashboards, or alerting systems - Machine‑readable logs for long‑term analysis - More consistent structure for automated tools Decision should consider simplicity vs. flexibility
mon self-assigned this 2026-04-07 11:01:16 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
bugfix/2
bugfix/1
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
mon
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mon/pb-dydns#6
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?