How to change Edge Component log levels

Sometimes, you’ll want to use a different value than an Agent Controller’s or Agent Proxy’s default value for logging. For example, when troubleshooting a problem with your agent or when trying out a new feature.

The following sections detail how to change the log level of your:

Agent Controller
Agent Proxy

See Log level reference for complete details about each agent’s log levels.

Change Agent Controller log level

Use the following tabs to set change your Agent Controller’s log level using the AEMBIT_LOG_LEVEL environment variable:

Virtual Machine
Windows

Log into your Agent Controller.
Open the Aembit Agent Controller service at /etc/systemd/system/aembit_agent_controller.service.

You may have to open this as root using sudo.

Under [Service], update or add Environment=AEMBIT_LOG_LEVEL=<log_level>, and set the log level you want. For example:

[Service]
...
User=aembit_agent_controller
Restart=always
Environment=AEMBIT_TENANT_ID=abc123
Environment=AEMBIT_DEVICE_CODE=
Environment=AEMBIT_AGENT_CONTROLLER_ID=A12345
Environment=ASPNETCORE_URLS=http://+:5000,http://+:9090
Environment=AEMBIT_LOG_LEVEL=<log_level>
StandardOutput=journal
StandardError=journal
...

Reload the Aembit Agent Controller config:
Terminal window
```
systemctl daemon-reload
```
Restart the Aembit Agent Controller service:
Terminal window
```
systemctl restart aembit_agent_controller.service
```

On Windows, you set the log level by passing AEMBIT_LOG_LEVEL as an MSI property when you install or upgrade Agent Controller.

Run msiexec to install or upgrade Agent Controller with AEMBIT_LOG_LEVEL set to your desired log level:

msiexec /i <agent_controller_msi> /l*v install.log `
  AEMBIT_TENANT_ID=<TENANT_ID> `
  AEMBIT_AGENT_CONTROLLER_ID=<CONTROLLER_ID> `
  AEMBIT_STACK_DOMAIN=<STACK_DOMAIN> `
  AEMBIT_LOG_LEVEL=<log_level>

Verify the log level change by checking Agent Controller logs at:
Terminal window
```
C:\ProgramData\Aembit\AgentController\Logs
```

Change Agent Proxy log level

Use the following tabs to set change your Agent Proxy’s log level using the AEMBIT_LOG_LEVEL environment variable:

Virtual Machine
Windows

Log into your Agent Proxy.
Open the Aembit Agent Proxy service at /etc/systemd/system/aembit_agent_proxy.service.

You may have to open this as root using sudo.

Under [Service], update or add Environment=AEMBIT_LOG_LEVEL=<log_level>, and set the log level you want. For example:

[Service]
...
User=aembit_agent_proxy
Restart=always
StandardOutput=journal
StandardError=journal
TimeoutStopSec=20
Nice=-20
LimitNOFILE=65535
Environment=AEMBIT_SIGTERM_STRATEGY=immediate
Environment=AEMBIT_AGENT_CONTROLLER=https://my-proxy-service:5000
Environment=AEMBIT_DOCKER_CONTAINER_CIDR=
Environment=CLIENT_WORKLOAD_ID=
Environment=AEMBIT_AGENT_PROXY_DEPLOYMENT_MODEL=vm
Environment=AEMBIT_SERVICE_PORT=51234
// highlight-next-line
Environment=AEMBIT_LOG_LEVEL=<log_level>
...

Reload the Aembit Agent Proxy config:
Terminal window
```
systemctl daemon-reload
```
Restart the Aembit Agent Proxy service:
Terminal window
```
systemctl restart aembit_agent_proxy.service
```

On Windows, you set the log level by passing AEMBIT_LOG_LEVEL as an MSI property when you install or upgrade Agent Proxy.

Run msiexec to install or upgrade Agent Proxy with AEMBIT_LOG_LEVEL set to your desired log level:

msiexec /i <agent_proxy_msi> /l*v install.log `
  AEMBIT_AGENT_CONTROLLER=<AC_HOSTNAME>:5000 `
  AEMBIT_LOG_LEVEL=<log_level>

Verify the log level change by checking Agent Proxy logs at:
Terminal window
```
C:\ProgramData\Aembit\AgentProxy\Logs
```
The ProgramData folder is hidden by default. To access it, open File Explorer, select View, and enable Hidden items.