[🐛 Bug]: The option on the AI Plugins page prompts "No AI enabled for this tenant".

[duguwo]

Describe the bug The option on the AI Plugins page prompts "No AI enabled for this tenant".

To Reproduce Steps to reproduce the behavior:

1. I have configured both OPENAI_BASE_URL and OPENAI_API_KEY in the environment section of the keep-frontend and keep-backend services within the docker-compose.common.yml file.
2. Start the service normally.
3. When checking the AI Plugins page of keep, it prompts "No AI enabled for this tenant".
4. When checking the logs of the keep - backend service, the following errors were found：

• dirname /venv/lib/python3.11/site-packages/keep/entrypoint.sh
• SCRIPT_DIR=/venv/lib/python3.11/site-packages/keep
• keep provider build_cache
• python /venv/lib/python3.11/site-packages/keep/server_jobs_bg.py /venv/lib/python3.11/site-packages/starlette/config.py:60: UserWarning: Config file '/venv/lib/python3.11/site-packages/keep/.env' not found. warnings.warn(f"Config file '{env_file}' not found.") /venv/lib/python3.11/site-packages/starlette/config.py:60: UserWarning: Config file '/venv/lib/python3.11/site-packages/keep/.env' not found. warnings.warn(f"Config file '{env_file}' not found.") 2025-03-05 01:03:45,720 [INFO] keep.cli.cli: Building providers cache 2025-03-05 01:03:45,721 [INFO] keep.providers.providers_factory: Loading providers

[dosubot[bot]]

The message "No AI enabled for this tenant" suggests that AI plugins are not activated for your tenant, even though you've configured OPENAI_BASE_URL and OPENAI_API_KEY. This might be due to the absence of AI algorithm configurations for your tenant. The system requires specific AI algorithms to be configured and enabled for your tenant to activate the AI plugins ^[1].

The warnings about the missing config file '/venv/lib/python3.11/site-packages/keep/.env' indicate that the application expects a configuration file at that location. This file might contain environment-specific settings or overrides, and its absence could affect the application's behavior or the availability of AI features ^[1].

To resolve these issues, ensure that AI algorithms are properly configured and enabled for your tenant. Additionally, check if the missing .env file is required for additional configurations. You may need to contact the Keep team to gain access to these features, as the AI plugins page suggests reaching out to them for access ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[duguwo]

Has anyone else encountered the same problem? Help!

[Cyberphysics]

还有人遇到过同样的问题吗？求助！

I meet same error in my keep instance whose version is Keep keep-0.1.83 and installed by helm chart in local k8s cluster. And I have integrate a LiteLLM in same namespace and I see the LLM of ollama in LiteLLM UI.

[shahargl]

@Matvey-Kuk can you please assist?

[kfkawalec]

I have the same problem with K8S. @Cyberphysics Did you manage to solve this problem?

[kfkawalec]

Well, I solved the first problem and enabled the configuration page. This requires setting a variable for the backend.

    - name: KEEP_EXTERNAL_AI_TRANSFORMERS_URL
      Value: http://litellm-service:4000

I can now see the configuration page. Currently, my logs are empty, but I have only a few alerts so far.

Execution logs:
Algorithm not executed yet.

I guess the documentation has gaps for a reason :)

[kfkawalec]

Update: I read the code more carefully.

"Transformers Correlation" is an AI Enterprise/Cloud feature that requires a dedicated ML service to train models on tenant data. This service must implement special Keep APIs (/remind_about_the_client, callback to Keep API, etc.).

So I disable this integration because it will not work in the on-premise version.