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

feat: how to monitor cortex inbound requests? #1007

Closed
Tracked by #1153
louis-jan opened this issue Aug 11, 2024 · 1 comment
Closed
Tracked by #1153

feat: how to monitor cortex inbound requests? #1007

louis-jan opened this issue Aug 11, 2024 · 1 comment
Labels
category: app shell Installer, updaters, distributions P1: important Important feature / fix type: feature request A new feature

Comments

@louis-jan
Copy link
Contributor

louis-jan commented Aug 11, 2024

Problem
I'm testing my copilot alternative setup, but I could not debug the outbound requests there. It would be great if I can debug inbound requests from cortex cli. For now, it just outputs the request path, no request body is logged.

Success Criteria
E.g.

1723389668 - Request /chat/completions
 { 
   "messages": [ 
      "role": "user", 
      "content": "hello" 
   ], 
   "stream": true, 
   "model": "llama3.1" 
}

Additional context
Add any other context or screenshots about the feature request here.

@louis-jan louis-jan added the type: feature request A new feature label Aug 11, 2024
@imtuyethan imtuyethan moved this to Icebox in Jan & Cortex Sep 2, 2024
@imtuyethan imtuyethan moved this from Icebox to Planning in Jan & Cortex Sep 2, 2024
@freelerobot freelerobot added category: app shell Installer, updaters, distributions P1: important Important feature / fix labels Sep 6, 2024
@dan-homebrew
Copy link
Contributor

Merged into #1153

@github-project-automation github-project-automation bot moved this from Planning to Completed in Jan & Cortex Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: app shell Installer, updaters, distributions P1: important Important feature / fix type: feature request A new feature
Projects
Archived in project
Development

No branches or pull requests

3 participants