---
title: "Set up the Grafana Enterprise Logs plugin for Grafana | Grafana Enterprise Logs documentation"
description: "Describes how to set up the Grafana Enterprise Logs plugin so that you can view your log data using Grafana."
---

# Set up the Grafana Enterprise Logs plugin for Grafana

## Requirements

Grafana Enterprise 7.3.0 or higher.

If you are using Kubernetes, refer to [Deploy Grafana Enterprise on Kubernetes](/docs/grafana/latest/setup-grafana/installation/kubernetes/#deploy-grafana-enterprise-on-kubernetes). Otherwise, refer to [Install Grafana](/docs/grafana/latest/setup-grafana/installation/).

## Install the plugin in your GEL instance

There are multiple ways to install the plugin in your local Grafana Enterprise instance. For more information, refer to [Grafana Enterprise Logs app installation](/grafana/plugins/grafana-enterprise-logs-app/).

## Enable and configure the plugin

1. Log in to your Grafana Enterprise Logs.
2. Go to the Config/Plugins page and select the Grafana Enterprise Logs (GEL) plugin from list.
3. From the configuration page of the plugin, enable the plugin by clicking on the “Enable plugin” button.
4. Provide the necessary API settings so that the plugin can connect to your cluster:

<!--THE END-->

- **Access Token**: Enter the admin-scoped access token that you generated when setting up your GEL cluster.
- **Grafana Enterprise Logs URL**: Enter the URL of your GEL cluster. For single-process clusters, this is any node in the cluster. For microservice deployments, the URL is the GEL gateway.
  
  [Configuration GEL plugin page](../../grafana-plugin-config-page.png)

<!--THE END-->

1. Click **Save API settings**.
2. Verify that the plugin loads and can communicate with the GEL admin API endpoints.
3. Navigate to the GEL plugin through the main menu to see the default access policy under the **Access Policies** tab.

### Configure the plugin via provisioning

You can alternatively manage the GEL plugin via a [plugin configuration](/docs/grafana/latest/administration/provisioning/#plugins) file.

Example plugin configuration file

#### Example GEL plugin configuration file

YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```yaml
apiVersion: 1

apps:
  # <string> the type of app, plugin identifier. Required
  - type: grafana-enterprise-logs-app
    # <integer> Org ID. Default to 1, unless org_name is specified
    org_id: 1
    # <string> Org name. Overrides org_id unless org_id not specified
    org_name: Main Org.
    # <boolean> disable the app. Default to false.
    disabled: false
    # <map> fields that will be converted to json and stored in jsonData.
    jsonData:
      # key/value pairs of string to object
      backendUrl: http://[...]
    # <map> fields that will be converted to json, encrypted and stored in secureJsonData. 
    secureJsonData:
      # <string> 
      accessToken: [...]
```

#### Optional `policiesOnly` field

For a simpler user experience that only shows the “Access policies” page, you can include the following in the `jsonData` configuration:

YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```yaml
jsonData:
  policiesOnly: true
```

This simpler mode of operation only gives users access to the ability to create access policies and tokens. It requires setting up the environment to include at least one tenant.

#### Legacy `base64EncodedAccessToken` field

Prior to version 6.0.0 of the plugin, a `base64EncodedAccessToken` field was required for authentication. This has been replaced with the simpler `accessToken`.

Troubleshooting for versions earlier than 6.0.0

```
</span>
```

The following is provided for troubleshooting purposes, or for users of versions earlier than 6.0.0.

Moving forward, use `accessToken` in your configuration.

If both `base64EncodedAccessToken` and `accessToken` are present in the `jsonData`, the `base64EncodedAccessToken` is ignored in versions 6.0.0 and later.

The format of the `base64EncodedAccessToken` token is a base64-encoded representation of a user-token pair, separated by a colon. For example, `$USER:$TOKEN`. If you’ve set your GEL token as the `TOKEN` environment variable, and you’ve also set a `USER` environment variable, then you can generate a compatible `base64EncodedAccessToken` token in the following format:

sh ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```sh
#USER INTENTIONALLY LEFT BLANK, INDICATING THE "ADMIN" USER
USER=
TOKEN=exampleTokenForBase64EncodedAccessToken
echo $USER:$TOKEN | tr -d '[:space:]' | base64 -w0
```

Though `$USER` is typically blank, you can opt to leave it in the expression to ensure that the `:` character is present. The following is a more direct way of obtaining the same result:

sh ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```sh
echo :$TOKEN | tr -d '[:space:]' | base64 -w0
```

These examples both result in the following `base64EncodedAccessToken` string:

![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```none
OmV4YW1wbGVUb2tlbkZvckJhc2U2NEVuY29kZWRBY2Nlc3NUb2tlbgo=
```

You can apply the encoded token string to the configuration under `secureJsonData` in your plugin configuration file:

YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```yaml
secureJsonData:
  # <string> a base64 encoding of $USER:$TOKEN
  base64EncodedAccessToken: OmV4YW1wbGVUb2tlbkZvckJhc2U2NEVuY29kZWRBY2Nlc3NUb2tlbgo=
```

## Next steps

Now that you have correctly configured the GEL app plugin, follow directions in [Set up a GEL tenant](../../tenant) and visualize your data.

## Limitations

The GEL plugin for Grafana allows to manage only 1 GEL cluster, and it doesn’t support managing multiple GEL clusters with a single GEL plugin installation. In case you need to manage multiple GEL clusters you should configure 1 GEL cluster per Grafana organization.