Add log level to either command line or config files for router and controller

[plorenz]

Right now you can only set log level to info (the default) or debug (using the -v flag). Should be able to select other log levels.

[pixitha]

Could we also look at adjusting this as well, the quotes around the code in ExecStart is invalid, so adding the logging stanza at the end, we have to manually edit this every time we build a service.

Default format:

[Unit]
Description=Ziti-Router for ad-use1-1.yaml
After=network.target

[Service]
User=root
WorkingDirectory=/opt/ziti
ExecStart="/opt/ziti/ziti-bin/ziti" router run "/opt/ziti/ad-use1-1.yaml.yaml"
Restart=always
RestartSec=2
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target

How we have to edit it

ExecStart=/opt/ziti/ziti-bin/ziti router run /opt/ziti/ad-use1-1.yaml --log-formatter pfxlog

[dovholuknf]

Interesting. I assume you've used the quickstart to generate the systemd file... What OS are you running and how does the error manifest that makes you need to update it like that?

[pixitha]

Ubuntu/Rhel8/Amazon Linux I think all use that same systemd file. We were having issues watching the logs in real time and found the pfxlog format easier to use.

https://openziti.discourse.group/t/log-tuning-for-ziti-router/1162 was the source for this issue.

We have really chatty services across the overlay and trying to find errors in real time when your working on a node was difficult.

[dovholuknf]

and found the pfxlog format easier to use

that's for sure! :) I do all my testing with Ubuntu and the systemd file that the quickstart generates has never been an issue. I wonder if it's a RHEL problem, i rarely try RHEL. I can try spinning up an amazon linux and see what happens. I'll also reach out to my systemd expert friend for RHEL help...

Just a 'for instance', I updated my current router to look like yours and you can see it somehow runs fine...

[plorenz]

@pixitha in case it's useful, you can also post-process the json to pfxlog format, either using the pfxlog binary, built from that repo, or by using the version built into ziti: ziti ops log-format. I do that regularly when debugging production systems, which require json for ingest, as it's easier to read.