Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wired and missing api calls in /metrics #2207

Open
ck3d opened this issue May 1, 2024 · 1 comment
Open

wired and missing api calls in /metrics #2207

ck3d opened this issue May 1, 2024 · 1 comment
Labels
bug Something isn't working unconfirmed

Comments

@ck3d
Copy link

ck3d commented May 1, 2024

I created multiple LocalAI integrations tests with the NixOS test infrastructure.
At end of each test, I dump the Prometheus metrics file as JSON format. The following test
https://github.com/ck3d/nix-local-ai/blob/main/local-ai/tests.nix#L181
creates following metrics.json.

The test calls following endpoinds each once:
/readyz
/v1/models
/v1/chat/completions
/v1/edits
/v1/completions
/metrics

The metrics files show wired api calls:

  1. method "GETT" which should be a "GET"
  2. endpoind "/metricsls", "/v1/compl", "/v1/completionstions" was not called
  3. no posts are listet

I did not check if the released LocalAI 2.13.0 has the same issue.

The test can be executed on a machine, which has nix installed, with following command:
nix build github:ck3d/nix-local-ai/1d0ae56380824349fd0590a2e1352ea42b129727#local-ai.tests.llama

@ck3d ck3d added bug Something isn't working unconfirmed labels May 1, 2024
@localai-bot
Copy link
Contributor

Hello,

Thank you for bringing this to our attention. As a bot, an experiment of @mudler, I have reviewed the details you've provided in the Github issue #2207. It seems that there are discrepancies in the API calls and their corresponding methods in the generated Prometheus metrics file. Moreover, some endpoints were not called at all.

The test output you shared indicates that some of the API calls are missing the correct HTTP method or have incorrect endpoint names. We will need to investigate this further and address the issue accordingly.

To expedite the resolution process, it would be helpful if you could confirm if the same issue persists in the released version of LocalAI 2.13.0. If it does, please provide any additional logs, screenshots, or test results that can assist in identifying the root cause.

For others experiencing the same issue, I recommend checking the status of this ticket and following the updates for any resolution. If necessary, feel free to comment on the issue and provide your own insights or tests results to help improve the investigation.

In the meantime, please let us know if there are any other concerns or issues you're facing with the LocalAI project. We appreciate your help in making LocalAI better and more efficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unconfirmed
Projects
None yet
Development

No branches or pull requests

2 participants