Troubleshooting Windows OpenTelemetry Collector

When installing OpenTelemetry (OTEL) Collector by LogicMonitor on your Windows server, you may encounter the following issue.

Error 1069 for Login Failure When Starting the LogicMonitor Collector Service

This error occurs because the account configured under the OTEL Collector service lacks the “Log on as a service” permission.
Windows requires this permission to enable service accounts to authenticate and run background processes.
The following image displays the error. 

Resolving Login Failure When Starting the LogicMonitor Collector Service

1. Log in to the Collector host using an account with Local Administrator privileges.
2. Open the command prompt or PowerShell and run the following command:
   secpol.msc
3. In the left panel, navigate to Local Policies > User Rights Assignment.
4. In the right panel, select Log on as a service.
5. Select Add User or Group.
6. In the Select Users or Groups modal, enter the account name that runs the LogicMonitor OTEL Collector service (for example, domain\collectoruser).
   You can retrieve the user account running the LogicMonitor OTEL Collector service by using the following command:
   sc.exe qc lmotel-wrapper
   
7. Select Check Names to validate, then select OK to save the policy updates.
8. Close the Local Security Policy Editor.
9. Restart the LogicMonitor OTEL Collector service from Services.msc or by running the following command:
   net start lmotel-wrapper
lmotel-wrapper is the service name of the OTEL Collector.

After these steps, the service starts without the login failure error.

LMOTEL Registration Failure When Using a Proxy

The LogicMonitor OpenTelemetry Collector (LMOTEL) running on Windows might shut down during startup when Collector registration fails to connect to the LogicMonitor portal through a required proxy server.

For LMOTEL running as the lmotel-wrapper Windows service, configure the proxy as service-specific environment variables. This configuration applies the proxy settings to the service instead of configuring proxy environment variables at the Windows machine level.

After configuring the environment variables, restart lmotel-wrapper for the changes to take effect.

Resolving LMOTEL Registration Failure

1. Open PowerShell as an administrator.
2. Run the following script to check the environment variables currently configured for the lmotel-wrapper service:

$ServiceName = "lmotel-wrapper"

$serviceRegPath = "HKLM:\SYSTEM\CurrentControlSet\Services\$ServiceName"

if (-not (Test-Path $serviceRegPath)) {
    Write-Error "Service '$ServiceName' not found in registry."
    exit 1
}

try {
    $envVars = (Get-ItemProperty `
        -Path $serviceRegPath `
        -Name Environment `
        -ErrorAction Stop).Environment
}
catch {
    Write-Output "No service-specific environment variables found for '$ServiceName'."
    return
}

$result = @{}

foreach ($entry in $envVars) {
    if ($entry -match '^(.*?)=(.*)$') {
        $key = $matches[1]
        $value = $matches[2]
        $result[$key] = $value
    }
}

$result.GetEnumerator() |
    Sort-Object Name |
    Format-Table -AutoSize

3. To configure the required proxy environment variables, replace <company_name> with the LogicMonitor account name and <proxy_url> with the proxy URL for your environment:

$ServiceName = "lmotel-wrapper"

$vars = @{
    LOGICMONITOR_ACCOUNT = "<company_name>"
    HTTPS_PROXY          = "<proxy_url>"
}

$serviceRegPath = "HKLM:\SYSTEM\CurrentControlSet\Services\$ServiceName"

if (-not (Test-Path $serviceRegPath)) {
    Write-Error "Service '$ServiceName' not found in registry."
    exit 1
}

$envList = @()

foreach ($key in $vars.Keys) {
    $envList += "$key=$($vars[$key])"
}

New-ItemProperty `
    -Path $serviceRegPath `
    -Name Environment `
    -PropertyType MultiString `
    -Value $envList `
    -Force | Out-Null

Write-Output "Environment variables have been configured for service '$ServiceName'."

This configuration creates environment variables for the lmotel-wrapper service. It does not configure HTTP_PROXY or HTTPS_PROXY as Windows machine-level environment variables.

4. If your environment requires both HTTP and HTTPS proxy configuration, include HTTP_PROXY and HTTPS_PROXY in $vars:

$vars = @{
    LOGICMONITOR_ACCOUNT = "<company_name>"
    HTTP_PROXY           = "<proxy_url>"
    HTTPS_PROXY          = "<proxy_url>"
}

5. Run the following command to restart LMOTEL so that the service uses the newly configured environment variables:

Restart-Service -Name "lmotel-wrapper"

6. Run the following command to check the service status:

Get-Service -Name "lmotel-wrapper"

Verify that the service reports a Running status.

7. Run the following script to verify that the expected service-specific environment variables are configured:

$ServiceName = "lmotel-wrapper"
$serviceRegPath = "HKLM:\SYSTEM\CurrentControlSet\Services\$ServiceName"

try {
    $envVars = (Get-ItemProperty `
        -Path $serviceRegPath `
        -Name Environment `
        -ErrorAction Stop).Environment

    $envVars
}
catch {
    Write-Output "No service-specific environment variables found for '$ServiceName'."
}

8. Verify the following after restarting LMOTEL:
   • The lmotel-wrapper service reports a Running status
   • The LMOTEL process remains running
   • Collector registration completes successfully
   • LMOTEL can communicate with the LogicMonitor portal through the configured proxy

The stronger validation criteria come from the proxy-access reference, which recommends validating the service, LMOTEL process, registration, and outbound proxy communication rather than relying only on the Windows service status.

9. If LMOTEL continues to experience registration or connectivity errors, check the following log file:

<installation_dir>\logicmonitor\lmotel\lmotel_windows.log

Review the log for Collector registration and connectivity errors. Verify that LMOTEL can complete Collector registration and connect to the LogicMonitor portal through the configured proxy.