Dear Product team,
In the metrics extension service on linux, the execstart information contains the parameter for loglevel = info. This setting is placed automatically in the systemd unit file. However we want to customize that on our servers. We can overwrite the execstart parameters but this is not a clean solution, because when a new version of the metrics extension is released, their might be new parameters in the execstart option. Since an override is in place those new parameters wont be applied because they are missing in the override.
Therefore we propose to work with a configuration file where we can specify the loglevel. So that on production servers we have only the errors reporterd and when an issue occurs we change the parameter for these servers and investigate the issue.
Thanks in advance for considering.
Thomas Baeck.
Dear Product team,
In the metrics extension service on linux, the execstart information contains the parameter for loglevel = info. This setting is placed automatically in the systemd unit file. However we want to customize that on our servers. We can overwrite the execstart parameters but this is not a clean solution, because when a new version of the metrics extension is released, their might be new parameters in the execstart option. Since an override is in place those new parameters wont be applied because they are missing in the override.
Therefore we propose to work with a configuration file where we can specify the loglevel. So that on production servers we have only the errors reporterd and when an issue occurs we change the parameter for these servers and investigate the issue.
Thanks in advance for considering.
Thomas Baeck.