Fix url to logql documentation (#2400)

pull/2406/head
Jérémy Farez 5 years ago committed by GitHub
parent 47aa1db44a
commit 2553d68ae3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 4
      docs/README.md

@ -41,7 +41,7 @@ simplifies the operation and significantly lowers the cost of Loki.
1. [Configuration](sources/clients/docker-driver/configuration.md)
4. [Fluent Bit](sources/../cmd/fluent-bit/_index.md)
3. [Fluentd](sources/clients/fluentd/_index.md)
7. [LogQL](sources/logql.md)
7. [LogQL](sources/logql/_index.md)
8. [Operations](sources/operations/_index.md)
1. [Authentication](sources/operations/authentication.md)
2. [Observability](sources/operations/observability.md)
@ -96,4 +96,4 @@ Images are sourced in this repo alonside content. They will sync to the website
When a PR is merged to master with changes in the `docs/sources` directory, those changes are automatically synched to the grafana/website repo and published to the staging site.
Generally, someone from marketing will publish to production each day, so as long as the sync is successful your docs edits will be published. Alternatively, you can refer to [publishing to production](https://github.com/grafana/website#publishing-to-production-grafanacom) if you'd like to do it yourself.
Generally, someone from marketing will publish to production each day, so as long as the sync is successful your docs edits will be published. Alternatively, you can refer to [publishing to production](https://github.com/grafana/website#publishing-to-production-grafanacom) if you'd like to do it yourself.

Loading…
Cancel
Save