apitech
/
loki
mirror of https://github.com/grafana/loki
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Like Prometheus, but for logs.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
9222 Commits
1162 Branches
364 Tags
731 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 5aa5bbecaf
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5aa5bbecaf'
${ noResults }
loki/docs/sources/operations/authentication.md

1.6 KiB
Raw Blame History

title menuTitle description weight
Manage authentication Authentication Describes how to add authentication to Grafana Loki. <nil>

Manage authentication

Grafana Loki does not come with any included authentication layer. Operators are expected to run an authenticating reverse proxy in front of your services.

The simple scalable deployment mode requires a reverse proxy to be deployed in front of Loki, to direct client API requests to either the read or write nodes. The Loki Helm chart includes a default reverse proxy configuration, using Nginx.

A list of open-source reverse proxies you can use:

{{< admonition type="note" >}} When using Loki in multi-tenant mode, Loki requires the HTTP header X-Scope-OrgID to be set to a string identifying the tenant; the responsibility of populating this value should be handled by the authenticating reverse proxy. For more information, read the multi-tenancy documentation.{{< /admonition >}}

For information on authenticating Promtail, see the documentation for how to configure Promtail.