Skip to content

[pull] master from netdata:master#1271

Merged
pull[bot] merged 6 commits into
webforfutureinc:masterfrom
netdata:master
Jun 19, 2026
Merged

[pull] master from netdata:master#1271
pull[bot] merged 6 commits into
webforfutureinc:masterfrom
netdata:master

Conversation

@pull

@pull pull Bot commented Jun 19, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

vkalintiris and others added 6 commits June 18, 2026 18:49
refactor(go.d/snmp-topology): extract topology Function package
#22771)

fix(journal-log-writer): reject non-absolute journal directory at startup

A relative journal_dir was accepted through Log::new init (the discarded
canonicalize result left the path relative), then failed at first write with a
cause-less "failed to create journal file in <path>" because
repository::File::from_path only accepts absolute paths. To OTLP clients this
surfaced as a permanent "Failed to write log entry" gRPC Internal error and
dropped log batches.

Validate that the journal directory is absolute as the first step of
create_chain, before any I/O, returning an InvalidPath error that names the
offending value, and enrich the residual create-file error to describe the real
remaining failure mode (unparseable generated file path).

Relative-path resolution stays the consumer's responsibility: netflow resolves
its relative default against the netdata cache dir when one is available, and
the new Log::new check is the safety net for the standalone case.

Add tests and a directory-contract spec; note the requirement in the stock otel
config.
@pull pull Bot locked and limited conversation to collaborators Jun 19, 2026
@pull pull Bot added the ⤵️ pull label Jun 19, 2026
@pull
pull Bot merged commit d47056a into webforfutureinc:master Jun 19, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants