Troubleshoot Telegraf Enterprise licensing

Use this page to diagnose common Telegraf Controller Enterprise license issues.

• License upload was rejected
• LICENSE_FILE_PATH is set but the license isn’t loaded
• Banners say “expired” but I just renewed
• Enterprise features are still disabled after applying a license
• Where to look in logs
• Get help

License upload was rejected

When a license upload fails validation, Telegraf Controller returns an error describing the cause. The previously active license (if any) is retained.

LICENSE_FILE_PATH is set but the license isn’t loaded

Work through this checklist:

• Is the file readable by the Telegraf Controller process? Check file permissions and the user account Telegraf Controller runs as. A permission-denied error on the file appears in the startup logs.
• Does the database already contain a license? LICENSE_FILE_PATH is consulted only when no license is stored in the database. To re-run bootstrap from LICENSE_FILE_PATH, first remove the existing license through the UI.
• Check the startup logs for the license bootstrap message. A successful bootstrap logs the license ID. A validation failure logs the reason. See Where to look in logs.

Banners say “expired” but I just renewed

License expiration status is re-evaluated hourly, so the status may not reflect a renewal until the next hourly check. To pick up the new license immediately, apply the renewed license through the UI—UI uploads take effect with no waiting.

Enterprise features are still disabled after applying a license

Verify the license is active:

1. Open Settings > Enterprise and confirm the license details are present and the status chip shows Valid.
2. From the API, call GET /api/license/entitlements and confirm the response shows "enterpriseEnabled": true.

If both look correct but a specific authentication provider (LDAP or OIDC) isn’t working, check whether the corresponding AUTH_LDAP_* or AUTH_OIDC_* environment variables were set before Telegraf Controller started. These variables are read at startup. If they were added or changed after Telegraf Controller started, restart Telegraf Controller so the new values take effect.

Where to look in logs

License-related events are written to the Telegraf Controller application logs (stdout and stderr by default).

Look for log lines containing:

• license: license bootstrap, validation, and replacement events.
• License bootstrap: the message emitted when LICENSE_FILE_PATH is processed at startup. A successful load includes the license ID; a failure includes the validation error.
• License upload: the message emitted when a license is uploaded through the UI.
• License expiration: messages emitted by the hourly expiration check when a license transitions between lifecycle states.

Get help

Contact InfluxData support for any licensing issue you can’t resolve from this page. When opening a support request, include:

• Your license ID (visible in Settings > Enterprise or in the GET /api/license response).
• The Telegraf Controller version.
• The exact validation error message if you encountered one.
• A relevant excerpt from the Telegraf Controller logs showing the problem.