Done
Details
Assignee
Boris IlijicBoris IlijicReporter
Santo LetoSanto LetoLabels
Planned Version/s
Needs QA
YesSprint
NoneFix versions
Priority
High
Details
Details
Assignee
Boris Ilijic
Boris IlijicReporter
Santo Leto
Santo LetoLabels
Planned Version/s
Needs QA
Yes
Sprint
None
Fix versions
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created December 21, 2023 at 11:25 AM
Updated December 12, 2024 at 5:47 PM
Resolved December 3, 2024 at 9:55 AM
Problem description
We cannot set a custom path for the log file or the log level. A customer prioritized the ability to set log path (in PMM agents and PBM agents) via a --log path options or better via the config file.
Solution proposition
It’ll be possible to start the PBM agent either with the command-line log option or with config, for example:
pbm-agent --mongodb-uri=mongodb://backupUser:test1234@192.168.56.96:27018/?authSource=admin --log-path=/tmp/pbm_log/test_command_line.log OR pbm-agent --config=/tmp/pbm.cfg
Command line options:
--log-path="/dev/stderr" path to file --log-json enable JSON output --log-level=debug minimal log level (options: "debug", "info", "warning", "error")
For a Kubernetes operator, environment variables could be used additionally.
Priorities of applying parameters:
Command line parameters
Environment variable
Configuration option
Acceptance Criteria
Ability to configure log path and level via configuration file
Ability to override log path and log level via command line
Default setting should be applied - default log path and log level if nothing was specified
Easy automation is possible to easily setup a consistent log path configuration across all PBM agents