Skip to content

[logs] reduce journal size by default#103

Merged
filanov merged 1 commit into
NVIDIA:mainfrom
noamhofshi:nhofshi/add-journal-size-flag
Apr 28, 2026
Merged

[logs] reduce journal size by default#103
filanov merged 1 commit into
NVIDIA:mainfrom
noamhofshi:nhofshi/add-journal-size-flag

Conversation

@noamhofshi
Copy link
Copy Markdown

@noamhofshi noamhofshi commented Apr 27, 2026

Reduce the journal size collection by default to 7 days instead of infinite.
Also added validation that we don't collect (by default) old "active" journal files from older OS installations.


Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines

  • x ] Is the commit message split over multiple lines and hard-wrapped at 72 characters?
  • Is the subject and message clear and concise?
  • Does the subject start with [plugin_name] if submitting a plugin patch or a [section_name] if part of the core sosreport code?
  • Does the commit contain a Signed-off-by: First Lastname email@example.com?
  • Are any related Issues or existing PRs properly referenced via a Closes (Issue) or Resolved (PR) line?
  • Are all passwords or private data gathered by this PR obfuscated?

Summary by CodeRabbit

  • New Features
    • Configurable time-window for journal log collection; shipped configs default to the last 7 days, with "all" available for unbounded capture.
  • Chores
    • Increased per-capture journal size in one shipped config and removed a global unbounded log setting in favor of the bounded option.
  • Tests
    • Updated and added tests validating both bounded (finite) and unbounded ("all") journal collection behaviors.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 27, 2026

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Adds a new logs.journal-since plugin option (default all) and sets it to -7days in three configs; plugin normalizes the option (treating "all"/empty as unbounded) and passes a --since cutoff to journalctl-backed captures; updates remove unconditional raw journal copying; tests added/updated to validate bounded and unbounded journal capture.

Changes

Cohort / File(s) Summary
Configuration Files
sos-mlx-cloud-verification.conf, sos-nvdebug.conf, sos-nvidia.conf
Introduce logs.journal-since = -7days under [plugin_options] to default journal capture to the last 7 days. sos-nvdebug.conf and sos-nvidia.conf remove a global all_logs = True setting; sos-nvidia.conf also increases journal_size (10 → 50) and documents per-capture size.
Logs Plugin Implementation
sos/report/plugins/logs.py
Add journal-since PluginOpt to LogsBase (default "all"); normalize "all"/empty to unbounded (None) during setup; pass the parsed since into add_journal calls for full, current, and previous boot captures; include LogsBase.option_list in CosLogs.option_list.
Tests
tests/report_tests/plugin_tests/logs.py
Modify existing LogsPluginTest to run with -k logs.journal-since=all; add JournalSinceFiniteTest (-24hours), JournalSinceAllTest (all), and JournalSinceDefaultTest (no -k) to assert correct --since propagation and default/unbounded behavior.

Sequence Diagram(s)

sequenceDiagram
    participant SosCLI as Sos CLI
    participant LogsPlugin as Logs Plugin
    participant Journalctl as systemd/journalctl
    SosCLI->>LogsPlugin: invoke with `logs.journal-since` option
    LogsPlugin->>LogsPlugin: normalize value → finite cutoff or `all` (None)
    alt cutoff is finite
        LogsPlugin->>Journalctl: run journalctl with `--since=<cutoff>`
    else cutoff is all
        LogsPlugin->>Journalctl: run journalctl without `--since`
    end
    Journalctl-->>LogsPlugin: return journal output
    LogsPlugin-->>SosCLI: bundle collected logs into report
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

🐰 I hopped through logs with a curious nose,

Seven days I marked where the fresh wind blows,
journalctl listens when I give the sign,
old heaps left behind, the new captures fine,
a tidy burrow of timestamps — all good, all mine.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title '[logs] reduce journal size by default' directly corresponds to the primary change: introducing a 7-day window for journal collection to reduce default captured logs.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

Comment thread sos/report/plugins/logs.py Fixed
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
sos/report/plugins/logs.py (1)

201-204: Prefer iterable unpacking for CosLogs.option_list.

This keeps the composition a bit clearer and avoids the extra list concatenation noted by lint.

♻️ Proposed refactor
-    option_list = LogsBase.option_list + [
-        PluginOpt(name="log-days", default=3,
-                  desc="the number of days logs to collect")
-    ]
+    option_list = [
+        *LogsBase.option_list,
+        PluginOpt(name="log-days", default=3,
+                  desc="the number of days logs to collect"),
+    ]
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@sos/report/plugins/logs.py` around lines 201 - 204, Replace the list
concatenation used to build option_list with iterable unpacking: instead of
option_list = LogsBase.option_list + [PluginOpt(...)] create a new list that
unpacks the base options and appends the new PluginOpt, e.g. option_list =
[*LogsBase.option_list, PluginOpt(name="log-days", default=3, desc="the number
of days logs to collect")]; update the assignment where option_list is defined
(referencing LogsBase.option_list and PluginOpt) so lint warnings about list
concatenation are eliminated.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@sos/report/plugins/logs.py`:
- Around line 17-35: The resolver currently advertised in
JOURNAL_SINCE_LONG_DESC is broader than what _resolve_journal_since_to_cutoff()
actually parses, causing unsupported inputs to silently fall back in
_collect_raw_journal(); update the code to either (A) extend
_resolve_journal_since_to_cutoff to accept systemd.time-like expressions
(support keywords like "now", "yesterday", "today", relative +/- prefixes, "X
unit" and "X unit ago" spans, space-separated spans, and common timezone-aware
timestamps—use a robust parser like python-dateutil or parsedatetime, normalize
to an mtime cutoff and return a timezone-aware datetime) and add clear logging
on parse failure, or (B) restrict JOURNAL_SINCE_LONG_DESC to exactly the
accepted patterns and add validation in _resolve_journal_since_to_cutoff that
logs/raises on unsupported inputs so _collect_raw_journal no longer silently
copies everything; refer to _resolve_journal_since_to_cutoff,
_collect_raw_journal, and JOURNAL_SINCE_LONG_DESC when applying the change.

---

Nitpick comments:
In `@sos/report/plugins/logs.py`:
- Around line 201-204: Replace the list concatenation used to build option_list
with iterable unpacking: instead of option_list = LogsBase.option_list +
[PluginOpt(...)] create a new list that unpacks the base options and appends the
new PluginOpt, e.g. option_list = [*LogsBase.option_list,
PluginOpt(name="log-days", default=3, desc="the number of days logs to
collect")]; update the assignment where option_list is defined (referencing
LogsBase.option_list and PluginOpt) so lint warnings about list concatenation
are eliminated.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: caff54c6-5963-4c16-9f7d-0e72ec8db254

📥 Commits

Reviewing files that changed from the base of the PR and between ea2ad0f and 9e85eb8.

📒 Files selected for processing (5)
  • sos-mlx-cloud-verification.conf
  • sos-nvdebug.conf
  • sos-nvidia.conf
  • sos/report/plugins/logs.py
  • tests/report_tests/plugin_tests/logs.py

Comment thread sos/report/plugins/logs.py
@noamhofshi noamhofshi force-pushed the nhofshi/add-journal-size-flag branch from 9e85eb8 to 3f7218a Compare April 27, 2026 18:46
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@sos/report/plugins/logs.py`:
- Around line 172-176: The glob returns sysroot-prefixed paths because pattern
is built with self.path_join(), but add_copy_spec() expects unprefixed paths and
will reapply sysroot; update the call in the loop so you strip the sysroot
before passing to add_copy_spec() by using self.strip_sysroot(path) instead of
path (locate the loop that uses self.path_join(..., "*.journal") and change the
argument to add_copy_spec accordingly), ensuring consistent behavior with other
usages (see add_copy_spec, path_join, strip_sysroot).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 030ef554-5d8c-4a2f-a9eb-079bd8efab43

📥 Commits

Reviewing files that changed from the base of the PR and between 9e85eb8 and 3f7218a.

📒 Files selected for processing (5)
  • sos-mlx-cloud-verification.conf
  • sos-nvdebug.conf
  • sos-nvidia.conf
  • sos/report/plugins/logs.py
  • tests/report_tests/plugin_tests/logs.py
✅ Files skipped from review due to trivial changes (3)
  • sos-nvdebug.conf
  • sos-nvidia.conf
  • sos-mlx-cloud-verification.conf
🚧 Files skipped from review as they are similar to previous changes (1)
  • tests/report_tests/plugin_tests/logs.py

Comment thread sos/report/plugins/logs.py Outdated
@noamhofshi noamhofshi force-pushed the nhofshi/add-journal-size-flag branch from 3f7218a to cde71e1 Compare April 27, 2026 18:56
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (2)
sos/report/plugins/logs.py (2)

177-180: Add inline comment to the except clause to satisfy CodeQL.

The rationale is already documented above the try block (lines 177–178), but CodeQL flags the empty except because the explanatory comment isn't syntactically inside the handler. Moving or duplicating the explanation satisfies the linter and keeps intent visible at the exception site.

📝 Suggested fix
                 try:
                     if os.path.getmtime(path) >= cutoff:
                         self.add_copy_spec(self.strip_sysroot(path))
-                # journald may rotate or vacuum a file between the glob
-                # and the stat, in which case we just skip it
                 except OSError:
-                    pass
+                    # journald may rotate/vacuum between glob and stat; skip
+                    pass
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@sos/report/plugins/logs.py` around lines 177 - 180, The empty except OSError
handler should include an inline explanatory comment to satisfy CodeQL; inside
the except OSError: block (the handler that currently only contains "pass")
duplicate the rationale already above the try — e.g., "journald may rotate or
vacuum a file between the glob and the stat, so skip this file" — so the
exception handling intent is documented at the exception site (leave the pass as
the behavior).

207-210: Consider iterable unpacking for modern Python style.

The concatenation works correctly, but PEP 448 iterable unpacking is considered more idiomatic. This is a minor stylistic preference.

♻️ Optional refactor
-    option_list = LogsBase.option_list + [
+    option_list = [
+        *LogsBase.option_list,
         PluginOpt(name="log-days", default=3,
                   desc="the number of days logs to collect")
     ]
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@sos/report/plugins/logs.py` around lines 207 - 210, The current code builds
option_list by concatenating LogsBase.option_list with a list literal; change
this to use PEP 448 iterable unpacking for a more idiomatic style by creating
option_list with unpacked items from LogsBase.option_list followed by the new
PluginOpt instance (referencing the option_list symbol and LogsBase.option_list
and PluginOpt to locate the change). Ensure the resulting option_list value is
equivalent to the original concatenation.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@sos/report/plugins/logs.py`:
- Around line 177-180: The empty except OSError handler should include an inline
explanatory comment to satisfy CodeQL; inside the except OSError: block (the
handler that currently only contains "pass") duplicate the rationale already
above the try — e.g., "journald may rotate or vacuum a file between the glob and
the stat, so skip this file" — so the exception handling intent is documented at
the exception site (leave the pass as the behavior).
- Around line 207-210: The current code builds option_list by concatenating
LogsBase.option_list with a list literal; change this to use PEP 448 iterable
unpacking for a more idiomatic style by creating option_list with unpacked items
from LogsBase.option_list followed by the new PluginOpt instance (referencing
the option_list symbol and LogsBase.option_list and PluginOpt to locate the
change). Ensure the resulting option_list value is equivalent to the original
concatenation.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7bbd4caf-89ae-405d-9144-ffe048575eeb

📥 Commits

Reviewing files that changed from the base of the PR and between 3f7218a and cde71e1.

📒 Files selected for processing (5)
  • sos-mlx-cloud-verification.conf
  • sos-nvdebug.conf
  • sos-nvidia.conf
  • sos/report/plugins/logs.py
  • tests/report_tests/plugin_tests/logs.py
✅ Files skipped from review due to trivial changes (2)
  • sos-nvdebug.conf
  • sos-mlx-cloud-verification.conf
🚧 Files skipped from review as they are similar to previous changes (1)
  • sos-nvidia.conf

@filanov
Copy link
Copy Markdown
Collaborator

filanov commented Apr 27, 2026

I can suggest a simplified version, support just duration of days and remove the all_logs flag from the default configuration, it is not needed anymore because since will get the right logs into sos_commands/logs, no need to store duplication of information by default.

Comment thread sos/report/plugins/logs.py Outdated
"/var/log/journal/*",
"/run/log/journal/*"
])
self._collect_raw_journal(since_arg)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggesting to avoid this part and instead remove the default all_logs that we set in the past form the config files, then if use want to collect the binary he will be able to do so but it's not really needed because add_journal will collect the output into the sos_commands/logs/

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done, removed it and reduced the custom filters I added

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
tests/report_tests/plugin_tests/logs.py (1)

23-31: ⚠️ Potential issue | 🔴 Critical

The test test_journal_runtime_collected will fail because raw journal files are not collected.

The plugin uses self.add_journal() to capture journal data via journalctl commands and output, but does not copy raw journal files from /var/log/journal/*. The --all-logs global flag affects output sizelimit only, not file copying. The test assertion at line 31 expects actual files matching /var/log/journal/* in the archive, which will not be present.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@tests/report_tests/plugin_tests/logs.py` around lines 23 - 31, The test fails
because raw journal files under /var/log/journal/* are not being copied—only
journalctl output is captured via self.add_journal(); update the plugin to also
copy raw journal files by adding a call to self.add_copy('/var/log/journal') or
self.add_copy('/var/log/journal/*') in the same place where add_journal is
invoked so the archive will contain the expected files for
test_journal_runtime_collected; reference the add_journal call and the
test_journal_runtime_collected assertion to locate where to add the copy.
🧹 Nitpick comments (1)
sos/report/plugins/logs.py (1)

126-129: Consider iterable unpacking (optional style improvement).

Ruff suggests using iterable unpacking for cleaner syntax. Both approaches are functionally equivalent.

♻️ Optional style improvement
-    option_list = LogsBase.option_list + [
+    option_list = [*LogsBase.option_list,
         PluginOpt(name="log-days", default=3,
                   desc="the number of days logs to collect")
     ]
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@sos/report/plugins/logs.py` around lines 126 - 129, The option_list
construction in logs.py currently concatenates lists; simplify the style by
using iterable unpacking: build option_list by using [*LogsBase.option_list,
PluginOpt(...)] instead of LogsBase.option_list + [...]; update the symbol
referenced (option_list, LogsBase.option_list, PluginOpt(name="log-days")) to
use the unpacking form for clearer, more idiomatic code.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@tests/report_tests/plugin_tests/logs.py`:
- Around line 23-31: The test fails because raw journal files under
/var/log/journal/* are not being copied—only journalctl output is captured via
self.add_journal(); update the plugin to also copy raw journal files by adding a
call to self.add_copy('/var/log/journal') or self.add_copy('/var/log/journal/*')
in the same place where add_journal is invoked so the archive will contain the
expected files for test_journal_runtime_collected; reference the add_journal
call and the test_journal_runtime_collected assertion to locate where to add the
copy.

---

Nitpick comments:
In `@sos/report/plugins/logs.py`:
- Around line 126-129: The option_list construction in logs.py currently
concatenates lists; simplify the style by using iterable unpacking: build
option_list by using [*LogsBase.option_list, PluginOpt(...)] instead of
LogsBase.option_list + [...]; update the symbol referenced (option_list,
LogsBase.option_list, PluginOpt(name="log-days")) to use the unpacking form for
clearer, more idiomatic code.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 568b429d-5948-4d81-b867-adaca5e43154

📥 Commits

Reviewing files that changed from the base of the PR and between cde71e1 and 569b697.

📒 Files selected for processing (3)
  • sos-nvidia.conf
  • sos/report/plugins/logs.py
  • tests/report_tests/plugin_tests/logs.py
🚧 Files skipped from review as they are similar to previous changes (1)
  • sos-nvidia.conf

self.add_journal(boot="this", tags='journal_since_boot')
self.add_journal(boot="last", tags='journal_last_boot')
if self.get_option("all_logs"):
self.add_copy_spec([
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need to delete this option, if user will want he can keep the journals, just need to remove this from the config files

Comment thread sos-nvdebug.conf Outdated
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need to disable that

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, kept it since I thought it makes sense for debug, removing

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's a name of a tool not a debug configuration.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
sos/report/plugins/logs.py (1)

78-93: ⚠️ Potential issue | 🟠 Major

Validate journal-since before passing it to add_journal().

add_journal() formats since into the journalctl command string, so forwarding raw config text here makes the new option shell-sensitive. Please escape or reject unsupported characters before calling the helper.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@sos/report/plugins/logs.py` around lines 78 - 93, Validate and sanitize the
user-provided since value (since_raw / since_arg from
get_option("journal-since")) before passing it to add_journal: accept only a
strict whitelist of safe formats (e.g., empty/"all", "boot"/"this"/"last"
keywords, ISO-8601 timestamps, or simple relative durations like "1h"/"30m") via
a regex/validator and reject or normalize anything containing shell-sensitive
characters (e.g., ; & | $ ` > < \\) or not matching the allowed patterns; if
validation fails, log a warning and set since_arg to None (or skip the
add_journal calls), then call add_journal with the validated/normalized
since_arg to avoid injecting unsanitized config into the journalctl command.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@sos/report/plugins/logs.py`:
- Around line 78-93: Validate and sanitize the user-provided since value
(since_raw / since_arg from get_option("journal-since")) before passing it to
add_journal: accept only a strict whitelist of safe formats (e.g., empty/"all",
"boot"/"this"/"last" keywords, ISO-8601 timestamps, or simple relative durations
like "1h"/"30m") via a regex/validator and reject or normalize anything
containing shell-sensitive characters (e.g., ; & | $ ` > < \\) or not matching
the allowed patterns; if validation fails, log a warning and set since_arg to
None (or skip the add_journal calls), then call add_journal with the
validated/normalized since_arg to avoid injecting unsanitized config into the
journalctl command.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 1655baec-5963-4916-83a5-5169706cfd73

📥 Commits

Reviewing files that changed from the base of the PR and between 569b697 and b2c3562.

📒 Files selected for processing (2)
  • sos-nvdebug.conf
  • sos/report/plugins/logs.py

Comment thread sos/report/plugins/logs.py Outdated
"expression (e.g. '-7days', '-24hours', '2 hours ago', "
"'yesterday', '2026-04-19', '2026-04-19 08:00:00'). Use "
"'all' (or leave empty) for no bound. Plugin default 'all', "
"overridden to '-7days' by sos-nvidia.conf, sos-nvdebug.conf, "
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i would not mention all the configuration files, just say by default config

Comment thread sos/report/plugins/logs.py Outdated
option_list = [
PluginOpt(name="journal-since", default="all", val_type=str,
desc=("journalctl --since value, or 'all' for no "
"bound (see systemd.time(7))"),
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

systemd.time(7) what does it mean?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a linux util that converts a number into days :)
Changed the comment to be clearer

Comment thread sos-nvdebug.conf Outdated
@@ -11,7 +11,6 @@ journal_size = 10
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should probably do the same as sos-nvidia.conf for this field

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, since now I removed the collect all logs by default it makes sense

Reduce the journal size collection by default to 7 days instead of
infinite.
And remove the auto collect of all the archives by default

Signed-off-by: Noam Hofshi <nhofshi@nvidia.com>
@noamhofshi noamhofshi force-pushed the nhofshi/add-journal-size-flag branch from 486f407 to e76e446 Compare April 28, 2026 12:13
@filanov filanov merged commit d690337 into NVIDIA:main Apr 28, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants