openlit / openlit

OpenLIT: Complete Observability and Evals for the Entire GenAI Stack, from LLMs to GPUs. Improve your LLM apps from playground to production πŸ“ˆ. Supports 20+ monitoring integrations like OpenAI & LangChain. Collect and Send GPU performance, costs, tokens, user activity, LLM traces and metrics to any OpenTelemetry endpoint in just one line of code.

Home Page:https://docs.openlit.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[FEAT]: Add `GET` for `/api/connections` endpoint in Ingester

patcher99 opened this issue Β· comments

πŸš€ What's the Problem?

Currently, there's no straightforward way for users to verify or view the configuration details of the observability platform they have set up to send LLM observability data to from Doku. This lack of transparency can lead to confusion or misconfiguration issues, as users cannot easily confirm the current setup.

πŸ’‘ Your Dream Solution

I envision a robust GET endpoint that users can call to retrieve the current configuration details of their observability platform. This endpoint would ideally return information such as the platform name (e.g., Grafana, NewRelic), API keys, the URLs for metrics and logs endpoints, any relevant usernames, and timestamps showing when the configuration was last updated.

πŸ€” Seen anything similar?

NA

πŸ–ΌοΈ Pictures or Drawings

No specific diagrams provided, but imagine a simple JSON structure depicting a clear, hierarchical organization of configuration details like

{
    "connections": {
        "apiKey": "xxx",
        "created_at": "2024-03-17T18:12:54Z",
        "logsUrl": "https://logxxx.com",
        "logsUsername": "123",
        "metricsUrl": "https://metrics.com",
        "metricsUsername": "123",
        "platform": "grafana"
    },
    "status": 200
}

πŸ‘ Want to Help Make It Happen?

  • Yes, I'd like to volunteer and help out with this!