-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
HTTP API Endpoint to get Loki version #3221
Comments
I like this request. One thing to note is that Grafana Cloud uses it's own internal release schedule which doesn't exactly correspond to Loki releases. However, Loki releases tend to be based on these internal builds which are then tagged & released as I think we should expose this information, but having a commit hash and a |
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Stalebot this is a really good idea, I promise |
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Plz stalebot have mercy on me |
* Return build info under `/version`. Closes #3221 * Update documentation. * Correct docs. * Format version handler code. * Ignore write error. * Sort imports. * Use `PrometheusVersion` struct. * Set Go version.
Is your feature request related to a problem? Please describe.
Prometheus has this endpoint:
GET /api/v1/status/buildinfo
which will return the version of Prometheus. I don't see any way using Loki's HTTP API to figure out what version of Loki I'm talking to.Describe the solution you'd like
GET /api/v1/status/buildinfo
or alternative for Loki.Additional context
I'm using Grafana Cloud, so I don't have any access or control over the Loki server. I don't know what version of Loki I'm using, I'd like to know so that I know when I can use new features that become available.
The text was updated successfully, but these errors were encountered: